Skip to content

fix(governance): separate public content reads from ruleset administration - #43

Merged
vitormattos merged 1 commit into
mainfrom
fix/governance-split-content-token-20261104
Nov 4, 2026
Merged

vitormattos merged 1 commit into
mainfrom
fix/governance-split-content-token-20261104

Conversation

@vitormattos

Copy link
Copy Markdown
Member

Problem

LibreCodeCoop's ruleset-management App has Administration (write), but not Contents (read). The current caller requests both, and its privileged Apply fails with GitHub HTTP 422 before reconciliation.

Changes

  • Optional contents-token input for a separate short-lived, read-only credential used only for public file classification.
  • Keep ruleset reads/writes, repository metadata, and classic protection preflight on the privileged installation token.
  • Require confirmed public repository metadata before using a separate contents token; fail closed for private/unverified repositories and failed content probes.
  • Regression tests and security/adoption documentation.

Validation

  • Node 24: TypeScript typecheck/build successful; 83 Vitest tests passed.
  • No rulesets, branch protections, secrets, or App permissions changed by this PR.
  • Signed/DCO commit 76fcdc8ae250c81aeb055533c2741385ac9f0b7b.

Deployment dependency

The LibreCodeCoop/.github caller must pin this signed commit and pass ${{ github.token }} as contents-token while retaining the protected ruleset-sync approval. Apply only after both PRs pass review/CI. The older caller's permission-contents: read cannot be removed until this engine revision is pinned.

…ation

Keep the GitHub App scoped to Administration (write), and use a separate read-only token for verified public content classification. Fail closed on private or unverified repository metadata; retain protected Apply review.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
@vitormattos
vitormattos merged commit bf77c5f into main Nov 4, 2026
8 checks passed
@vitormattos
vitormattos deleted the fix/governance-split-content-token-20261104 branch November 4, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant