{"version":"2.1.208","anchor":"github-repo-visibility-and-branch-protection-context","canonical_anchor":"github-repo-visibility-and-branch-protection-context","heading":"GitHub repo visibility and branch protection context","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208\/e\/github-repo-visibility-and-branch-protection-context","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208","markdown":"### GitHub repo visibility and branch protection context\n\n**What**\n\nClaude now gathers repository visibility (public\/private), branch protection rules, and rulesets from GitHub via `gh` when working in a git repository. This gives Claude better context for decisions about pushing, branching, and code review workflows.\n\n**Details**\n\n- Uses `gh` CLI to query `\/rulesets?per_page=100` and `\/branches?protected=true&per_page=100`\n- Includes org-level sibling repo docs (top 50 by `pushedAt`)\n- Degrades gracefully when `gh` is unavailable, unauthenticated, or the token lacks org scope \u2014 each section shows a \"not queryable here\" marker rather than failing\n- Org\/repo docs are candidates only \u2014 Claude filters to those whose org already appears in known repo facts\n\n**Evidence**\n\nNew repo context gathering (search for `\"Repo visibility & branch protection (via gh)\"` and `\"\/rulesets?per_page=100\"`)"}