nixpkgs/.github/ISSUE_TEMPLATE.md

## Issue description


### Steps to reproduce


## Technical details

<!-- Please insert the output of running `nix-shell -p nix-info --run "nix-info -m"` below this line -->
simplify ISSUE_TEMPLATE 2016-03-31 16:14:54 +02:00			`## Issue description`
.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-22 23:46:01 +01:00


simplify ISSUE_TEMPLATE 2016-03-31 16:14:54 +02:00			`### Steps to reproduce`
.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-22 23:46:01 +01:00


simplify ISSUE_TEMPLATE 2016-03-31 16:14:54 +02:00			`## Technical details`
.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-22 23:46:01 +01:00
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> 2023-10-09 02:35:10 +02:00			<!-- Please insert the output of running `nix-shell -p nix-info --run "nix-info -m"` below this line -->