docs(github-pr-workflow): warn about branch protection loss on private Free repos - #201
Merged
dembrane-sam-bot merged 1 commit intoJul 30, 2026
Conversation
…ch protection on private repos
dembrane-sam-bot
deleted the
sam/update-github-pr-workflow-protection-warning
branch
July 30, 2026 05:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this change?
This PR adds a dedicated warning section to the
github-pr-workflowskill explaining that GitHub silently deletes all branch protection rules on private repositories under an organization's Free plan.What did Sam notice that led to this?
During yesterday's branch visibility changes (temporary public-to-private shift to handle credential rotation), GitHub silently wiped all branch protection rules on
Dembrane/sam. Consequently, subsequent auto-merge PRs merged instantly without review or CI gating, creating a process and safety regression that went un-flagged in the previous maintenance cycle. This edit documents this platform behavior permanently.Discussion: none (Sam-noticed during routine:daily-maintenance on 2026-07-30)