summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
Commit message (Collapse)AuthorAgeFilesLines
* CONTRIBUTING: UpdatesMatthias Clasen2023-02-061-1/+2
| | | | | | Mention matrix instead of irc, and ask for display/graphics as essential info in issues.
* Update references to master in the repositoryMatthias Clasen2021-11-291-1/+1
|
* Update contribution guideMatthias Clasen2020-12-051-0/+6
| | | | Make my feelings about bug reporting by screencast known.
* Update CONTRIBUTING.mdMatthias Clasen2020-05-061-6/+1
| | | | | | | Point to discourse, rather than mailing lists. Based on a suggestion by sujiniku, https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1763
* rename CODE-OWNERS to CODEOWNERSTimm Bäder2020-01-081-1/+1
| | | | gitlab reads the new filename but not the old one.
* docs: Fix GTK links and locationsEmmanuele Bassi2019-02-061-2/+2
|
* docs: Clarify the section on dependenciesEmmanuele Bassi2018-12-281-4/+21
|
* docs: Clarify the section on commit accessEmmanuele Bassi2018-12-281-5/+6
| | | | | The section is about rules for direct commit access to the upstream repository, so let's be more clear about it.
* docs: Clarify autoclosing issues syntaxEmmanuele Bassi2018-12-281-12/+9
| | | | | | Link to the GitLab documentation, and clarify that if no single commit in a merge requests closes an issue, you should add a reference to the issue in the commit message anyway.
* docs: Make the contribution guide slightly more friendlyEmmanuele Bassi2018-12-281-33/+141
| | | | | | | | | | | This is an important document for newcomers, so we should err on the side of being more detailed on what kind of contributions we expect, and how we expect them. The text is heavily modelled on the contributing-template by Nadia Eghbal available here: https://github.com/nayafia/contributing-template
* docs: Move commit style docs to the contribution guideEmmanuele Bassi2018-12-281-6/+84
| | | | | There's no point in having a separate file detailing how commits ought to work, considering we already have a contribution guide.
* docs: README.commits converted to markdownRobert Roth2018-08-261-3/+3
|
* docs: Start defining the owners of code sectionscode-ownersEmmanuele Bassi2018-04-161-1/+3
| | | | | | | | | | | | | | | | When filing a new merge request it's often hard to know who to ask for a review; using the Git log doesn't always help — the person that touched a file last may just be fixing the build or a compiler warning. The `CODE-OWNERS` file format is something that GitHub uses in order to pre-fill the list of reviewers: https://help.github.com/articles/about-codeowners/ Ideally, in the future, we'll be able to use this file with a bot like homu to automatically go through newly filed merge requests and automatically ask the relevant people for reviews, instead of doing this manually.
* docs: Style fixes for the contribution guidelinesEmmanuele Bassi2018-03-241-8/+8
|
* Update CONTRIBUTING.mdEmmanuele Bassi2018-03-131-11/+34
| | | Update the instructions to match the GitLab workflow.
* Rename 'HACKING' to 'CONTRIBUTING'Emmanuele Bassi2017-08-141-0/+40
And remove redundant and obsolete information.
View Lorry Controller Status