Context
From health check report #33 — Recommendation #2.
Problem
The donpetry-bot PAT (DON_PETRY_BOT_PETRY_PROJECT_PAT) cannot push to PR head branches it doesn't own. For PRs opened from branches inside petry-projects/* repos where the bot is not a collaborator with push rights, GitHub's API rejects branch-update requests with 403.
Proposed Fix
Either:
- Add
donpetry-bot as a collaborator with Write or Maintain role on each repo in petry-projects org, OR
- Create a scoped GitHub App installation token with
contents: write on petry-projects (more secure than a broad PAT)
Expected Impact
Restores auto-rebase functionality; removes the root cause of the 403.
Urgency
HIGH — without write access the 403 is permanent; every PR that falls behind main will fail to get the auto-rebase.
Context
From health check report #33 — Recommendation #2.
Problem
The
donpetry-botPAT (DON_PETRY_BOT_PETRY_PROJECT_PAT) cannot push to PR head branches it doesn't own. For PRs opened from branches insidepetry-projects/*repos where the bot is not a collaborator with push rights, GitHub's API rejects branch-update requests with 403.Proposed Fix
Either:
donpetry-botas a collaborator withWriteorMaintainrole on each repo inpetry-projectsorg, ORcontents: writeonpetry-projects(more secure than a broad PAT)Expected Impact
Restores auto-rebase functionality; removes the root cause of the 403.
Urgency
HIGH — without write access the 403 is permanent; every PR that falls behind main will fail to get the auto-rebase.