shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-02-04 17:47:03 +03:00
Code
systemd-stable/.github/ISSUE_TEMPLATE/Bug_report.md

23 lines
563 B
Markdown
Raw Normal View History

github: use multiple issue templates Github now has issue templates in the web interface, and allows more than one to be specified. Let's split our single template in two: bug report and RFE.
2018-05-10 09:01:22 +02:00
---
name: Bug report
about: A report of an error in a recent systemd version
---
**systemd version the issue has been seen with**
> ...
<!-- **NOTE:** Do not submit bug reports about anything but the two most recently released systemd versions upstream! -->
docs: move markdown docs from .github/ to docs/ The GitHub guide on contributing file says: "Decide whether to store your contributing guidelines in your repository's root, docs, or .github directory." https://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file But there's really no advantage to keeping it in the hidden .github/, since these are public and really belong together with the other documentation. We can still keep the issue templates under .github/, since they are not really documentation on their own. Updated the links pointing to CONTRIBUTING.md to refer to the one in docs/.
2018-09-07 01:07:06 -07:00
<!-- For older version please use distribution trackers (see https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md#filing-issues). -->
github: use multiple issue templates Github now has issue templates in the web interface, and allows more than one to be specified. Let's split our single template in two: bug report and RFE.
2018-05-10 09:01:22 +02:00
**Used distribution**
> …
**Expected behaviour you didn't see**
> …
**Unexpected behaviour you saw**
> …
**Steps to reproduce the problem**
Copy Permalink