Скачать или смотреть How to Restrict Team Members from Merging Changes in GitHub Repositories

Learn how to effectively limit merge permissions for team members in GitHub repositories and ensure that only you can approve changes.
---
This video is based on the question https://stackoverflow.com/q/63645217/ asked by the user 'shivansh shrivastava' ( https://stackoverflow.com/u/11718288/ ) and on the answer https://stackoverflow.com/a/63651835/ provided by the user 'HamiltonPharmD' ( https://stackoverflow.com/u/14122375/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to restrict team members from merging the changes that they did in there forked repository to base repository?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Restrict Team Members from Merging Changes in GitHub Repositories

When collaborating on a software project, it's crucial to maintain control over your codebase, especially when it comes to merging changes from team members. If you're using GitHub, you may find that your collaborators can merge their changes back to your base repository without your explicit permission. This can lead to unintended consequences and conflicts in your project's code. In this guide, we will explore how you can restrict team members from merging their changes directly into your base repository, allowing you to review their contributions first.

The Problem

Imagine you've created a base repository and invited your friend to be a collaborator. They fork your repository, make changes, and submit a pull request (PR). However, they also have the ability to merge those changes into your main repository without your permission. This situation not only poses risks to your project's integrity but also undermines the review process which is essential for maintaining high-quality code.

Why This Happens

By default, GitHub allows collaborators to have broad access to repositories, which includes the ability to merge pull requests. To continue collaborating effectively and securely, you need to know how to fine-tune these permissions.

The Solution: Protecting Your Branch

To prevent your collaborators from merging their changes directly into your base repository, you can set up branch protection rules in your GitHub repository settings. Here’s a step-by-step guide to achieving that:

Step-by-Step Instructions

Open the Settings Tab

Navigate to your GitHub repository and look for the Settings tab located at the top right of the screen.

Select Branches

From the left-hand column, click on Branches to access branch management functionalities.

Choose the Branch to Protect

Identify the branch you want to restrict (typically, this will be your main or master branch) and choose it.

Add a Protection Rule

To the right of Branch Protection Rules, click on Add Rule to define your protection parameters.

Specify the Branch Name

In the Branch name pattern field, enter the exact name of the branch you want to protect.

Require Pull Request Reviews

Select Require pull request reviews before merging. This ensures that no one can merge changes without your approval.

Alternatively, you can select Require review from Code Owners if you have designated specific individuals to review changes.

Create the Rule

Once you've configured your rules, click the green Create button at the bottom of the form.

And that's it! You have successfully set up branch protection, allowing for a more controlled and reviewed merging process in your GitHub repository.

Conclusion

By restricting the merge capabilities of your team members, you maintain better oversight of the code being integrated into your main project. This not only allows you to ensure the quality of contributions but also fosters a more structured workflow where changes pass through review, minimizing the risk of conflicts and bugs in your codebase.

Now, you can invite your friends to contribute with the confidence that you have the final say on what gets merged into your repository. Happy coding!