Ruleset to allow non-PR pushes on a specific folder #156761
Replies: 1 comment
-
|
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
In an existing repository we require pull requests before merging. I want to allow pushes directly to the main branch as long as the changes are only in one specific folder (and subfolder): docs.
This will allow us to keep enforcing code reviews via PR but loosen those requirements regarding docs changes. This enable us to support some auto-commit-push scenarios when updating docs content which would be desired in our case.
From my understanding rulesets seems what would give us such flexibility, but it seems to me I would need to list all non docs folders to apply the branch protection, instead of loosing the restriction in docs. This has the effect that any top level folder would allow non-PR changes which is not desired.
Any suggestion on how to loose the "require pull requests before merging" on a specific folder?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions