`nix-info -m` outputs Markdown, so it makes more sense to include it in
issues verbatim than within a preformatted code block.
Co-authored-by: Gavin John <gavinnjohn@gmail.com>
Where this was a markdown heading, it sometimes had the wrong weight
so it appeared as if it was a subheading of the previous section, and
some people feel the word "Priorities" creates misleading
expectations.
Link: https://github.com/NixOS/nixpkgs/pull/203969/files#r1037761779
Adds a small text to each issue and the PR template to encourage people to use
👍's for issues they're also interested in. See
https://github.com/NixOS/nix.dev/issues/359 for more information
Co-Authored-By: Valentin Gagarin <valentin.gagarin@tweag.io>
It's nice to be able to easily create an issue for an unreproducibility,
but my additional motivation for creating this issue template is that it
makes it easier for non-maintainers to create issues that are correctly
tagged '8.topic: reproducible builds'.
When I started out, I was confused by this section and no idea what to put in
and I don't think I'm the only one as I rarely see it filled out.
This means there isn't much usefulness in it for bot processing either; better
just remove it.
This is really essential thing that everyone should be doing.
A few extra notifications won't hurt anyone, and we should be tracking issues
to connect them to the best people who can handle them.
Co-Authored-By: Cole Helbling <cole.e.helbling@outlook.com>
Create new categories for the issues:
* Bug report
* Packaging request
* Security
Add metadata information to the issues so that we may match issues to
maintainers using a bot in the future.
The old `.github/ISSUE_TEMPLATE.md` is being used by the "Open a regular
issue." link.
