We tried, but GitHub's markdown renderer will render these newlines
there, so going back to "real" paragraphs.
Also fixed the emphasis slightly, since "via Issues" is not bold, "via a
Pull Request" is also made not bold for consistency. Puts the focus more
on the "contribute" link as well.
This isn't an issue template; it's a stub that will be auto-closed by CI
and is meant to discourage future package requests, and encourage more
pull requests.
See the full discussion on https://github.com/NixOS/nixpkgs/issues/425040.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
Most workflow files are already well formatted, but to make it easier to
keep it that way, we can add yamlfmt.
I personally have a preference for non-indented arrays for YAML, but
wanted to avoid bigger diffs here - the status-quo clearly are indented
arrays.
Some changes are made manually to the get-merge-commit action and the
issue templates. Those would otherwise make yamlfmt misbehave on those.
25.11 is the current unstable, while 25.05 was promoted to stable and 24.11 is on its way to deprecation.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
The Package Request form no longer exists, so it makes no sense to mention it. We used to direct update requests to forks there, instead, users can now mention forks in the Additional Context section added in this commit.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
The out of date package report was split into two forms: an update request and a backport request.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
One for generic package issues, one for NixOS (Module)
issues, and one for Darwin-specific issues.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
`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
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'.
