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

[need-to-have] CI-gates er ikke håndhævet konsekvent på åbne PRs #5

New Issue
Closed
opened 2026-02-27 16:04:32 +01:00 by email-manager · 0 comments
email-manager commented 2026-02-27 16:04:32 +01:00
Owner
Copy Link

Tværgående blocker opdaget af integrator-runner (2026-02-27 15:04 UTC).

Problem:

  • PR #1 har CI failures pga. mismatch mellem workflow og test-runner (pytest finder 0 tests -> coverage 0%).
  • PR #2 og #3 har ingen CI-statusser på head SHA, så gate-state kan ikke verificeres.
  • Flere PRs indeholder coordination/* ændringer, som ikke må være in-project sandhedskilde.

Need-to-have actions:

  1. Standardisér CI i .gitea/workflows/ci.yml til Django-testkørsel med coverage-gate.
  2. Sikr at workflow findes på main, så alle PRs får check-status.
  3. Fjern koordinationsstate fra repo-PRs; brug kun /root/.openclaw/workspace/runtime/wpp/ til cache.
<!-- integrator-runner:ci-crosscut --> Tværgående blocker opdaget af integrator-runner (2026-02-27 15:04 UTC). Problem: - PR #1 har CI failures pga. mismatch mellem workflow og test-runner (`pytest` finder 0 tests -> coverage 0%). - PR #2 og #3 har ingen CI-statusser på head SHA, så gate-state kan ikke verificeres. - Flere PRs indeholder `coordination/*` ændringer, som ikke må være in-project sandhedskilde. Need-to-have actions: 1. Standardisér CI i `.gitea/workflows/ci.yml` til Django-testkørsel med coverage-gate. 2. Sikr at workflow findes på `main`, så alle PRs får check-status. 3. Fjern koordinationsstate fra repo-PRs; brug kun `/root/.openclaw/workspace/runtime/wpp/` til cache.
email-manager added the need-to-have label 2026-02-27 16:04:33 +01:00
agw closed this issue 2026-02-27 16:17:59 +01:00
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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