systemd - systemd

	Commit message (Collapse)	Author	Age	Files	Lines
*	github: add systemd-vmspawn to the issue templates	Kristian Klausen	2024-04-15	2	-0/+2
\|
*	github: bump version in template	Yu Watanabe	2023-12-24	2	-5/+5
\|
*	github: update default and example in template	Yu Watanabe	2023-03-15	2	-5/+5
\|
*	Update github issue template to include systemd-dissect	Cornelius Hoffmann	2023-03-15	2	-0/+2
\|
*	doc: correct wrong use "'s" contractions	Jan Engelhardt	2023-03-07	1	-1/+1
\|
*	github: update version in bug templates	Zbigniew Jędrzejewski-Szmek	2022-12-20	2	-2/+2
\|
*	issue-templates: Add note about updating labeling policy	Jan Macku	2022-09-07	2	-0/+4
\|
*	Add systemd-hwdb to bug/RFE templates	Daan De Meyer	2022-07-15	2	-0/+2
\|
*	Add coredump daemons to bug/RFE template component options	Daan De Meyer	2022-07-13	2	-0/+4
\|
*	github: add more components to RFE issue template	Jan Macku	2022-06-27	1	-3/+44
\| \| \| \|	Follow-up to: #23838
*	github: add more components to issue template	Yu Watanabe	2022-06-27	1	-3/+44
\|
*	github: Update issue templates to issue forms	Jan Macku	2022-06-23	4	-64/+215
\| \| \| \| \| \| \| \| \|	Issue forms templates allow us to add automation in place. This patch replaces old markdown issue templates with new issue forms. It also adds workflow to automatically mark issues by component label based on reported data. This change could help with initial triaging of issues.
*	github: point to "tags" instead of "releases" in systemd-stable	Frantisek Sumsal	2022-01-23	1	-1/+1
\| \| \| \| \| \|	since we don't do releases there. Mentioned in https://github.com/systemd/systemd/issues/22230#issue-1111991271.
*	github: mention the systemd-devel ML in the new issue tab	Frantisek Sumsal	2021-12-07	1	-0/+9
\|
*	licensing: say that our github docs are LGPLv2.1+	Zbigniew Jędrzejewski-Szmek	2021-10-01	2	-2/+2
\| \| \| \|	This mirros what 0aff7b7584 did for docs/.
*	docs: link to stable releases in the bug template	Zbigniew Jędrzejewski-Szmek	2021-03-25	1	-2/+4
\| \| \| \| \|	Also, ask people to use a recent stable release and provide useful version information. Inspired by #19118.
*	github: expressly ask for logs in github issue template	Lennart Poettering	2021-02-10	1	-0/+12
\| \| \| \| \|	Apparently it's not obvious that logs are a good thing to provide, hence let's explicitly ask for them.
*	github: ask for systemd version in RFE form	Lennart Poettering	2021-02-06	1	-0/+3
\| \| \| \| \| \|	It happens too often that what people ask for already is implemented. Let's help cut the noise a bit, and make people check things first hopefully, and at least make it either for us to detect such cases.
*	markdown: fix comment	Lennart Poettering	2021-01-19	1	-1/+1
\| \| \| \|	Follow-up for 2d816c9804c1d565797faff85c0fdbfb15f1e9d5
*	markdown: suggest backticks around uname -a output	Lennart Poettering	2021-01-19	1	-1/+4
\| \| \| \|	Fixes: #18238
*	github: ask for arch+kernel in bug report form	Lennart Poettering	2020-10-02	1	-1/+8
\| \| \| \| \| \| \|	Quite often we see kernel and arch specific issues, let's ask for the version right-away when people file the issue. Other tweaks.
*	docs: point contributors to list of most recent systemd releases	Lennart Poettering	2020-06-10	1	-1/+2
\| \| \| \|	Fixes: #16083
*	github: use systemd.io links in issue template	Lennart Poettering	2019-12-16	1	-1/+1
\|
*	docs: move markdown docs from .github/ to docs/	Filipe Brandenburger	2018-09-08	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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/.
*	github: use multiple issue templates	Zbigniew Jędrzejewski-Szmek	2018-05-10	2	-0/+36
	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.