summaryrefslogtreecommitdiffstats
path: root/.github (follow)
Commit message (Collapse)AuthorAgeFilesLines
* FUNDING: this needs to be yamlZbigniew Jędrzejewski-Szmek2019-07-081-1/+1
|
* Create FUNDING.ymlZbigniew Jędrzejewski-Szmek2019-07-081-0/+1
|
* docs: move markdown docs from .github/ to docs/Filipe Brandenburger2018-09-083-50/+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/.
* docs: move doc/ to docs/Filipe Brandenburger2018-09-081-2/+2
| | | | | | | | | The docs/ directory is special in GitHub, since it can be used to serve GitHub Pages from, so there's a benefit to switching to it in order to expose it directly as a website. Updated references to it from the documentations themselves, from the CONTRIBUTING.md file and from Meson build files.
* github: use multiple issue templatesZbigniew Jędrzejewski-Szmek2018-05-103-31/+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.
* doc: add a new doc/ directory, and move two markdown docs into themLennart Poettering2018-02-271-2/+2
| | | | | | | | | I figure sooneror later we'll have more of these docs, hence let's give them a clean place to be. This leaves NEWS and README/README.md as well as the LICENSE texts in the root directory of the project since that appears to be customary for Free Software projects.
* Docs: Fix spelling and capitalization (#7408)longersson2017-11-211-1/+1
|
* CONTRIBUTING: stop mentioning "make check"Michael Biebl2017-08-211-1/+1
| | | | | Since the switch to meson this information is no longer valid. HACKING already documents how to run the test suite. See #6642
* github: how to report bugs for older distribution versions (#6146)Lukáš Nykrýn2017-06-202-0/+7
|
* github: tweak the issue template a bit moreLennart Poettering2017-06-191-1/+1
|
* github: tweak the issue template a bit, comment moreLennart Poettering2017-06-191-2/+2
|
* github: comment out submitter note in ISSUE_TEMPLATEMantas Mikulėnas2017-05-221-1/+1
| | | | It's for the person filling in the form, not for people reading it later.
* github: remove checkboxes from ISSUE_TEMPLATEMantas Mikulėnas2017-05-221-2/+4
| | | | The issue list page thinks those are in fact todo items.
* docs: use https in the mailing list urlAsciiWolf2017-03-071-1/+1
|
* docs: add a note about reporting security vulns (#5541)Zbigniew Jędrzejewski-Szmek2017-03-071-0/+4
| | | | | | | | We *do* have the occasional security issue, where it would be nice to have non-public disclosure and time to fix the issue before it's fully public. Our github infrastracture does not make it easy to report vulnerabilities in confidential manner, so let's leverage the distro mechanisms for that. I think we're better off with this solution than leaving it up to individual reporters to discover some mechanism on their own.
* CONTRIBUTING: reword the part about unsetting the label (#4716)Zbigniew Jędrzejewski-Szmek2016-11-231-1/+1
| | | Only project members can do it.
* documentation: add a short document describing how to test your systemd ↵Lennart Poettering2016-07-211-0/+1
| | | | build tree (#3763)
* Add RELEASE.md file which lists the steps needed for releaseZbigniew Jędrzejewski-Szmek2016-06-131-0/+12
| | | | | I put it in .github, so it doesn't stand out too much; after all it's not interesting to most people.
* CONTRIBUTING: ask people to comment after after force-pushZbigniew Jędrzejewski-Szmek2016-06-131-0/+1
|
* CONTRIBUTING: remove line wrappingZbigniew Jędrzejewski-Szmek2016-06-131-17/+8
| | | | | GitHub displays this file poorly, because it preserves the newlines. Let's try how things look without any wrapping.
* CONTRIBUTING: recommend force-push (#3273)Zbigniew Jędrzejewski-Szmek2016-05-161-4/+1
|
* .github/ISSUE_TEMPLATE: Use a list for submission type so that it appears as ↵daurnimator2016-02-251-3/+2
| | | | a checkbox
* github: add a basic issue templateLennart Poettering2016-02-211-0/+29
| | | | | | As documented here: https://help.github.com/articles/creating-an-issue-template-for-your-repository/
* github: move CONTRIBUTING.md into .github subdirectoryLennart Poettering2016-02-211-0/+37
As suggested by: https://github.com/blog/2111-issue-and-pull-request-templates
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 05:21:26 +0100