From 28cbb91d663df3859b8414fb898b3d7cccc05dc7 Mon Sep 17 00:00:00 2001 From: anyreso Date: Sat, 13 Apr 2024 15:48:06 -0400 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20update=20CONTRIBUTING.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 452f2ee..76bae31 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,10 +34,10 @@ If you want to contribute changes without write access to the repository, you ca 4. After you've made your changes, you commit them locally and push these back to your fork on gitlab. 5. Finally, you can [create a merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html#when-you-work-in-a-fork) from your fork's branch to upstream's branch. -Creating a merge request notifies project maintainers that you've made changes and allows them to review your code and potentially merge it into the main project. - > We encourage you to [allow commits from upstream members](https://docs.gitlab.com/ee/user/project/merge_requests/allow_collaboration.html#allow-commits-from-upstream-members) so that they can [push to the fork as the upstream member](https://docs.gitlab.com/ee/user/project/merge_requests/allow_collaboration.html#push-to-the-fork-as-the-upstream-member) in order for you to reach out for help. +Creating a merge request notifies project maintainers that you've made changes and allows them to review your code and potentially merge it into the main project. + When your branch is merged, you may want to [update your fork](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#update-your-fork) to be synced with upstream. ## Repository membership