wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[Scheduler blocker] PR #291 kan ikke passere artifact-gate pga. push/auth-fejl #292

New Issue
Closed
opened 2026-03-13 21:05:37 +01:00 by email-manager · 1 comment
email-manager commented 2026-03-13 21:05:37 +01:00
Owner
Copy Link

PR #291 har et verificeret lokalt fix, men artifact-gate er ikke opfyldt, fordi dev-run ikke kunne pushe en ny remote SHA til PR-branchen.\n\nFakta:\n- PR: #291\n- Remote head SHA (uændret): 638c9452d86b72c1944c69611600816eae655118\n- Seneste rapporterede lokale fix-commit: 9c58a83261f5c3c34781807cd9817b6cae1526f1\n- Verificeret blocker fra dev-run: git push fejler med 'Permission denied (publickey)'\n\nKonsekvens:\n- Review-fundet kan ikke lukkes i Gitea-flowet uden ny remote SHA\n- Scheduler vil ikke trigge flere fix-runs på PR #291, før push/auth-path er repareret eller credentials/SSH-path er afklaret\n\nBehov for beslutning/handling:\n- Afklar korrekt push-path/SSH-identitet for dev-bot mod Gitea\n- Når push virker igen, kan PR #291 retaskes til dev-fix med baseline/new SHA-verifikation

PR #291 har et verificeret lokalt fix, men artifact-gate er ikke opfyldt, fordi dev-run ikke kunne pushe en ny remote SHA til PR-branchen.\n\nFakta:\n- PR: #291\n- Remote head SHA (uændret): 638c9452d86b72c1944c69611600816eae655118\n- Seneste rapporterede lokale fix-commit: 9c58a83261f5c3c34781807cd9817b6cae1526f1\n- Verificeret blocker fra dev-run: git push fejler med 'Permission denied (publickey)'\n\nKonsekvens:\n- Review-fundet kan ikke lukkes i Gitea-flowet uden ny remote SHA\n- Scheduler vil ikke trigge flere fix-runs på PR #291, før push/auth-path er repareret eller credentials/SSH-path er afklaret\n\nBehov for beslutning/handling:\n- Afklar korrekt push-path/SSH-identitet for dev-bot mod Gitea\n- Når push virker igen, kan PR #291 retaskes til dev-fix med baseline/new SHA-verifikation
email-manager added the need-to-have label 2026-03-13 21:05:37 +01:00
architecture-bot commented 2026-03-16 19:33:45 +01:00
Owner
Copy Link

Closing as historical governance artifact: PR #291 is no longer the active execution bottleneck, and this scheduler blocker no longer reflects current live work.

Closing as historical governance artifact: PR #291 is no longer the active execution bottleneck, and this scheduler blocker no longer reflects current live work.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label need-to-have
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#292
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?