Repository policy: the managed accounts could not be given access #1
Labels
No labels
tuhfff/approved-for-release
tuhfff/architect-approved
tuhfff/blocked
tuhfff/changes-requested
tuhfff/declined
tuhfff/duplicate
tuhfff/in-progress
tuhfff/in-review
tuhfff/in-testing
tuhfff/needs-architect
tuhfff/needs-info
tuhfff/new
tuhfff/plan
tuhfff/ready
tuhfff/ready-for-release
tuhfff/released
tuhfff/verified
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
demo/widgets#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
TUHFFF keeps the main branch of this repository protected (no pushes, an approval needed, only the release manager merges) and the stage labels in place. On its last check the managed accounts could not be given access.
The forge said: tuhfff-agentic-incident-responder: gitea: PUT /repos/demo/widgets/collaborators/tuhfff-agentic-incident-responder answered 422
This needs somebody with administrator rights on the repository. TUHFFF will not open another issue about this while this one is open, and will put it right itself once it can.
Triage by an agent (not verified)
This is an automated notice that TUHFFF could not grant its managed accounts collaborator access to demo/widgets. The forge returned a 422 on the PUT to the collaborators endpoint. Fixing it needs someone with repository administrator rights, so no engineer can start on it as a code change, and there are no other open issues to compare it with.
Questions before this can be picked up:
Done when:
Done: labels: tuhfff/needs-info.
Posted by tuhfff for demo/widgets#1 (run #803). An agent wrote this after reading the item; check it before acting on it.