feat: [12] Branch-Protection per Authorized Integration (JWT) mit PAT-Fallback #53
No reviewers
Labels
No labels
auto-merge
bug
chore
dependency
duplicate
enhancement
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
hobbypunk/rails-base_app!53
Loading…
Reference in a new issue
No description provided.
Delete branch "enhancement/12_protection_pat"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Der erste Live-Run des Reconcile-Jobs scheiterte mit 403 ("user should be an owner or a collaborator with admin write of a repository") – der ephemeral
secrets.GITHUB_TOKENdarf die Branch-Protection-API nicht.Lösung: Authorized Integration (bevorzugt) statt breitem PAT
Forgejo-Doku-Empfehlung wörtlich: "Authorized Integrations are preferred over using Access Tokens whenever possible."
branch-protection.yml), Git-Ref (refs/heads/main), Eventwrite:repository(deckt/repos/*inkl.branch_protections)Implementiert
enable-openid-connect: trueim Workflow (JWT-Mint durch den Runner)audience: gesetzt → Skript holt JWT per OIDC und authentifiziert mitAuthorization: bearer; leer → Fallback auf statischen Token (secrets.FORGEJO_TOKEN || secrets.GITHUB_TOKEN) – hält Template-Repos ohne Integration lauffähigTo-do (einmalig, in deinen User-Settings)
hobbypunk/rails-base_app, Workflow file =branch-protection.yml, Git ref =refs/heads/main, Event =push(oder leer)write:repositoryaudience:-Input eintragen (PR-Feedback oder nach dem Merge – leer lassen funktioniert bis dahin über den Fallback)[12] Branch-Protection: PAT fuer Admin-API (FORGEJO_TOKEN)to feat: [12] Branch-Protection: PAT fuer Admin-API (FORGEJO_TOKEN)feat: [12] Branch-Protection: PAT fuer Admin-API (FORGEJO_TOKEN)to feat: [12] Branch-Protection per Authorized Integration (JWT) mit PAT-Fallback📊 Coverage
Patch-Coverage: keine getrackten Zeilen geändert
Schwächste Dateien im Projekt
🔍 Report im Browser ansehen · 📄 Run-Artifact „coverage-report“