| Age | Commit message (Collapse) | Author |
|---|
|
it's annoying to write issues with the checklist in the way, and the
proposal is more important.
|
|
since the installer prompts users to file issues, labelling them
automatically should reduce triaging effort significantly.
|
|
decided on the @NixOS/documentation-team, see NixOS/nix.dev#359 for more information
|
|
according to [GitHub documentation] some fields are required.
`about` is not listed, but it probably is required.
[GitHub documentation]: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms
|
|
markdown would interpret parentheses as belonging to the first link without escaping.
|
|
this allows anyone to create labelled issues for easy filtering.
|
|
each change should be an improvement, a label for that is redundant.
|
|
|
|
|
