mirror of
https://github.com/NixOS/nixpkgs.git
synced 2024-11-22 15:03:28 +00:00
54e4669c75
`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>
42 lines
951 B
Markdown
42 lines
951 B
Markdown
---
|
|
name: Build failure
|
|
about: Create a report to help us improve
|
|
title: 'Build failure: PACKAGENAME'
|
|
labels: '0.kind: build failure'
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
### Steps To Reproduce
|
|
|
|
Steps to reproduce the behavior:
|
|
1. build *X*
|
|
|
|
### Build log
|
|
|
|
```
|
|
log here if short otherwise a link to a gist
|
|
```
|
|
|
|
### Additional context
|
|
|
|
Add any other context about the problem here.
|
|
|
|
### Notify maintainers
|
|
|
|
<!--
|
|
Please @ people who are in the `meta.maintainers` list of the offending package or module.
|
|
If in doubt, check `git blame` for whoever last touched something.
|
|
-->
|
|
|
|
### Metadata
|
|
|
|
<!-- Please insert the output of running `nix-shell -p nix-info --run "nix-info -m"` below this line -->
|
|
|
|
---
|
|
|
|
Add a :+1: [reaction] to [issues you find important].
|
|
|
|
[reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/
|
|
[issues you find important]: https://github.com/NixOS/nixpkgs/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc
|