Commit graph

22 commits

Author SHA1 Message Date
piegames 177b80f61d
Merge pull request #204460: Issue template improvements
Issue template improvements
2023-02-07 17:03:14 +01:00
Arnout Engelen f15edf0630
Fix issue template for unreproducible packages 2023-01-07 11:17:58 +01:00
piegames 483c606a94 fixup! .github/ISSUE_TEMPLATE: Improvements 2022-12-27 13:12:12 +01:00
piegames 5507007730
Update .github/ISSUE_TEMPLATE/missing_documentation.md
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2022-12-15 23:27:58 +01:00
piegames a2719e490d .github/ISSUE_TEMPLATE: Improvements 2022-12-04 12:25:43 +01:00
Arnout Engelen c6cdcfc10c
Merge pull request #192724 from raboof/add-unreproducible-package-issue-template
Add issue template for unreproducible packages
2022-11-14 09:07:49 +01:00
Valentin Gagarin 3bc2971030 fix typo 2022-10-04 22:45:57 +02:00
Valentin Gagarin a919cae175 fix typo 2022-09-30 12:05:50 +02:00
Arnout Engelen 2018f92ef2
Add issue template for unreproducible packages
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'.
2022-09-25 22:33:46 +02:00
Valentin Gagarin 7bbf2cd29a issue template: fill 'about' field
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
2022-09-19 10:08:02 +02:00
Valentin Gagarin 8277d18445 add issue template for missing or incorrect documentation
this allows anyone to create labelled issues for easy filtering.
2022-09-16 09:57:32 +02:00
Artturin d46665e879 ISSUE_TEMPLATE/build_failure.md: create 2022-05-09 15:43:53 +03:00
K0RR 6daff24989
out_of_date_package_report.md: fix typo 2022-02-03 18:15:29 +08:00
Atemu 0c408a087b
bug_report.md: remove confusing 'maintainer information' section (#120711)
When I started out, I was confused by this section and no idea what to put in
and I don't think I'm the only one as I rarely see it filled out.

This means there isn't much usefulness in it for bot processing either; better
just remove it.
2021-12-23 15:21:48 +01:00
Kreyren 055926dc48
github/bug_report: Improve readability 2021-07-23 03:57:56 +02:00
Narice 7f271858cd modified out-of-date template
Changed the label to '9.needs: package (update)'
Removed trailing spaces
Modified formulation of a sentence
2020-10-22 11:29:39 +02:00
Narice 5837209891 improved out-of-date template 2020-10-21 13:13:59 +02:00
Narice 32535c94a0 added out-of-date package reports to templates 2020-10-14 10:39:33 +02:00
worldofpeace 29efd1e6a4 bug_report.md: ask to notify maintainers
This is really essential thing that everyone should be doing.
A few extra notifications won't hurt anyone, and we should be tracking issues
to connect them to the best people who can handle them.

Co-Authored-By: Cole Helbling <cole.e.helbling@outlook.com>
2020-04-13 18:03:05 -04: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 2a227c6cd8
.github/ISSUE_TEMPLATE/security.md: remove
since the .github/SECURITY.md was added in the org-level repo, there are
now two entries in the list. So remove this-one.
2019-07-26 15:33:26 +02: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