Disable fork syncing with rulesets

[ishaan-mehta]

Select Topic Area

Question

Body

Is there a way to disable fork syncing with rulesets? I know it is possible with branch protection rules but cannot find the equivalent rule in rulesets.

[ibra-kdbra]

Disabling fork syncing in GitHub using rulesets isn't directly supported in the same way that branch protection rules are implemented.

[ishaan-mehta]

I see, thanks, @ibra-kdbra — so it is not possible at all with rulesets?

If that is the case, is there any way an org admin could disable fork syncing across multiple repositories in a dynamic way (like we can do with custom properties for other rules)? Or do branch protection rules have to be individually set up for the 100s of repositories in our org that need fork syncing disabled?

[ibra-kdbra]

It's not fully possible, but making it for 100 repos will be too much work.

Rulesets don't currently support fork syncing control, you can automate branch protection rules using the GitHub API or GitHub CLI.
Writing a script that applies branch protection rules across all repositories may help. This could target hundreds of repositories dynamically.

While there's no explicit setting for fork syncing, you could write a custom action or app(GitHub actions or Github apps) that enforces the behavior you need (e.g., preventing merges from forked repositories unless specific conditions are met)

API Endpoint: PUT /repos/{owner}/{repo}/branches/{branch}/protection
You can find more details in the github-docs

If all I mentioned above(automation work) doesn't serve your needs, the only way to manually apply branch protection rules is through the repository settings UI, though this isn't feasible for 100s of repositories without some form of scripting.

[opwx]

Here are the steps to create a branch protection rule:

Navigate to the main page of the repository.
Under your repository name, click Settings.
In the "Code and automation" section of the sidebar, click Branches.
Next to "Branch protection rules", click Add rule.
Under "Branch name pattern", type the branch name or pattern you want to protect.
Optionally, enable required pull requests.
Optionally, enable required status checks.
Optionally, select Require conversation resolution before merging.
Optionally, select Require signed commits.
Optionally, select Require linear history.
Optionally, to merge pull requests using a merge queue, select Require merge queue.
Optionally, to choose which environments the changes must be successfully deployed to before merging, select Require deployments to succeed before merging, then select the environments.
Optionally, make the branch read-only.
Optionally, select Do not allow bypassing the above settings.
You can also manage rulesets for a repository by navigating to the repository settings and selecting "Rulesets" under "Code and automation"

Here are the steps to manage rulesets:

Navigate to the main page of the repository.
Under your repository name, click Settings.
In the "Code and automation" section of the sidebar, click Rulesets.
Click New ruleset.
Enter a name and description for the ruleset.
Optionally, add a trigger to the ruleset.
Optionally, add an action to the ruleset.
Click Create ruleset.

[ibra-kdbra]

try to use your brain, dear user...

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬