summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorMatthias Clasen <mclasen@redhat.com>2021-11-29 17:37:49 -0500
committerMatthias Clasen <mclasen@redhat.com>2021-11-29 17:37:49 -0500
commitddd5704c923c412ce9024a8383b56d09a8b11950 (patch)
tree5d4faf384a9cf9f44f804fdca0ccb6708e8c2a16 /CONTRIBUTING.md
parent3ba6d2bd27823dc7f60dd027f77de3a0f457ba86 (diff)
downloadgtk+-ddd5704c923c412ce9024a8383b56d09a8b11950.tar.gz
Update references to master in the repository
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 80be9420fc..cde57475f0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -256,7 +256,7 @@ people committing to GTK to follow a few rules:
0. Always write a meaningful commit message. Changes without a sufficient
commit message will be reverted.
-0. Never push to the `master` branch, or any stable branches, directly; you
+0. Never push to the `main` branch, or any stable branches, directly; you
should always go through a merge request, to ensure that the code is
tested on the CI infrastructure at the very least. A merge request is
also the proper place to get a comprehensive code review from the core