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

Integrator merge blocker: PR #283 is merge-ready but Gitea merge API returns HTTP 405 #284

New Issue
Closed
opened 2026-03-13 10:38:49 +01:00 by integrator-bot · 0 comments
integrator-bot commented 2026-03-13 10:38:49 +01:00
Owner
Copy Link

Observed during integrator run for PR #283.

Facts:

  • PR #283 head SHA: db7be0dfc6
  • Approved review present
  • Terminal CI state: success
  • gitea-api pr state 283 reports merge_ready=true
  • Local read-only merge simulation against main shows no conflicts
  • Repeated gitea-api pr merge 283 as INTEGRATOR returns HTTP 405 with message: "Please try again later"

Impact:

  • Integrator cannot complete merge of a merge-ready PR
  • Likely cross-cutting Gitea/project merge-state issue rather than a code issue in PR #283

Requested follow-up:

  • Inspect server-side mergeability / branch-protection state for PR #283 and other merge-ready PRs
  • Confirm whether Gitea merge endpoint is temporarily stuck or misreporting mergeability
Observed during integrator run for PR #283. Facts: - PR #283 head SHA: db7be0dfc66bf102a8bbd8f4ca4ddccc4680e9e4 - Approved review present - Terminal CI state: success - gitea-api pr state 283 reports merge_ready=true - Local read-only merge simulation against main shows no conflicts - Repeated `gitea-api pr merge 283` as INTEGRATOR returns HTTP 405 with message: "Please try again later" Impact: - Integrator cannot complete merge of a merge-ready PR - Likely cross-cutting Gitea/project merge-state issue rather than a code issue in PR #283 Requested follow-up: - Inspect server-side mergeability / branch-protection state for PR #283 and other merge-ready PRs - Confirm whether Gitea merge endpoint is temporarily stuck or misreporting mergeability
agw closed this issue 2026-03-13 12:18:15 +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
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#284
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?