Setting branch protection rules on a private repository #60566
Replies: 2 comments
-
|
🕒 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.
-
|
I have contacted sales team support about this as well. The documentation is contradictory in separate places. I'm surprised there hasn't been more questions about this online like Stackoverflow. It doesn't make sense that an individual dev should pay for Team when i'm not working in a team! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
My friend who has GitHub Pro tried enforcing branch protection rules on their private repository, but it tells them that "Your rules won't be enforced on this private repository until you move to a GitHub Team or Enterprise organization account". I thought that GitHub Pro accounts could set branch rules?
Beta Was this translation helpful? Give feedback.
All reactions