chore: remove unused file

[Malix-Labs]

This file is unused and not displayed, since there are files in .github/ISSUE_TEMPLATE

Its content can be used if an equivalent form is created in .github/ISSUE_TEMPLATE AND .github/ISSUE_TEMPLATE/config.yml > blank_issues_enabled: false

But right now, there is no .github/ISSUE_TEMPLATE/config.yml file, and so blank_issues_enabled defaults to true

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

[SigmaSquadron]

Not true. This file is used when someone decides to open a blank issue. You have misinterpreted the documentation you linked.

Additionally, please review our commit conventions. We do not use the feat/chore nomenclature in Nixpkgs.

[Malix-Labs]

Not true. This file is used when someone decides to open a blank issue. You have misinterpreted the documentation you linked

I tested it beforehand, and this is not the case on my end :

• 
• 

Please test on your end

Additionally, please review our commit conventions. We do not use the feat/chore nomenclature in Nixpkgs

I know. I have no idea what to call it otherwise (except "config", "github", ... ?), feel free to propose what I should call it instead

And apparently I'm not alone to not know : https://github.com/NixOS/nixpkgs/commits/master/.github/ISSUE_TEMPLATE.md

[Malix-Labs]

^ @SigmaSquadron please review #521074 (comment)

[Malix-Labs]

I made some more tests with some different configuration, and I couldn't make the blank template have a default template like what is suggested in the doc.

This PR should be reopened

[SigmaSquadron]

Reopened why, exactly? All you've proven here is that GitHub is inconsistently applying their own documentation to the issue creation forms. Once they fix this bug, (and this is a bug as their own documentation describes a different behaviour) we would be left with no blank issue template if this is merged.

I don't see a benefit to removing a tiny file that may be useful for us in the future when GitHub fixes this bug. Honestly, there are far more pressing matters to attend to in Nixpkgs than trying to flip-flop between whatever GitHub is doing at any given moment.

[Malix-Labs]

I will ask GitHub if it's a bug and should be resolved or if it's a deprecated feature (since it seems to be according to the "legacy" wording)

[Malix-Labs]

See #44311

[Malix-Labs]

Confirmed as deprecated : github/docs#44312 (comment)

Please reopen this PR

[SigmaSquadron]

There is no need to request my review before you address my previous reviews. This still does not follow our commit conventions.