Commit Graph

8 Commits

Author SHA1 Message Date
Victor Engmark
54e4669c75 docs: Clarify how to provide technical details/metadata
`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>
2024-10-25 10:12:44 +02:00
Eelco Dolstra
1d59cdcb2a ISSUE_TEMPLATE: 'nix run' -> 'nix-shell -p'
'nix run' is an experimental command.
2020-01-05 22:47:43 +01:00
zimbatm
5cece63aad
github: use the new issue template (#64983)
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.
2019-07-22 09:04:00 +00:00
Graham Christensen
cec203be16
ISSUE_TEMPLATE: replace technical details withh nix-info 2017-11-13 20:44:52 -05:00
Alexey Shmalko
f5bed28db8
github issue template: add sandboxing info 2017-05-01 15:38:11 +03:00
Jakob Gillich
0d091ffd4a simplify ISSUE_TEMPLATE 2016-03-31 16:14:54 +02:00
Eelco Dolstra
830c2d6389 ISSUE_TEMPLATE.md: Tweak 2016-02-23 17:06:55 +01:00
zimbatm
4ba3c96431 .github/ISSUE_TEMPLATE.md - get more information
The goal is to get all the necessary information from the reporter upfront.
Too many times the issues submits and we need to do a round of asking before
we can get close to a solution.
2016-02-23 12:09:41 +00:00