summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorSonny Piers <sonny@fastmail.net>2021-03-01 09:44:58 +0100
committerSonny Piers <sonny@fastmail.net>2021-03-01 09:45:41 +0100
commitff0e498668bb46ae681fc653fb491bdb1bb76865 (patch)
treec568c7cc73350b1476731be2930eb29696598a09 /CONTRIBUTING.md
parent7ba6bbfec8a1ef790d738f2e90aadcd7d9bbb05f (diff)
downloadgjs-ff0e498668bb46ae681fc653fb491bdb1bb76865.tar.gz
Document how to run without installing
Closes #381
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md7
1 files changed, 1 insertions, 6 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index fee21ad8..8783f348 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -84,11 +84,6 @@ Next, read the [workflow guide to contributing to GNOME][workflow].
(In short, create a fork of the repository, make your changes on a
branch, push them to your fork, and create a merge request.)
-If your contribution fixes an existing issue, please refer to the issue
-in your commit message with `Closes #123` (for issue 123).
-Otherwise, creating a separate issue is not required.
-See the section on "Commit messages" below.
-
When you submit your merge request, make sure to click "Allow commits
from contributors with push access".
This is so that the maintainers can re-run the GitLab CI jobs, since
@@ -319,7 +314,7 @@ For further guidelines about line length and commit messages, read
If the commit is related to an open issue in the issue tracker, note
that on the last line of the commit message. For example, `See #153`, or
`Closes #277` if the issue should be automatically closed when the merge
-request is accepted.
+request is accepted. Otherwise, creating a separate issue is not required.
## Thanks ##