Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 6 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Document closed-not-merged PR reconciliation rules #51

New Issue
Closed
opened 2026-07-02 03:14:32 -05:00 by jcwalker3 · 2 comments
jcwalker3 commented 2026-07-02 03:14:32 -05:00
Owner
Copy Link
Copy Source

A bad state occurred around PR #47 / issue #46:

  • PR #47 became closed.
  • Gitea reported PR #47 as not merged.
  • PR #47 had no merge commit in PR metadata.
  • Issue #46 was closed.
  • Issue #46 still had status:in-progress.
  • prgs/master advanced to a #46-related commit.
  • The reviewer correctly stopped because the normal 'PR is open' gate failed.

This means the content may have landed on master, but the PR/issue metadata did not reflect a normal merge. The workflow needs explicit rules for detecting, stopping, reconciling, and reporting this state.

A bad state occurred around PR #47 / issue #46: * PR #47 became closed. * Gitea reported PR #47 as not merged. * PR #47 had no merge commit in PR metadata. * Issue #46 was closed. * Issue #46 still had `status:in-progress`. * `prgs/master` advanced to a #46-related commit. * The reviewer correctly stopped because the normal 'PR is open' gate failed. This means the content may have landed on master, but the PR/issue metadata did not reflect a normal merge. The workflow needs explicit rules for detecting, stopping, reconciling, and reporting this state.
jcwalker3 commented 2026-07-02 03:14:33 -05:00
Author
Owner
Copy Link
Copy Source

Claimed. status:in-progress

Claimed. status:in-progress
jcwalker3 commented 2026-07-02 04:46:32 -05:00
Author
Owner
Copy Link
Copy Source

Reconciliation: PR #52 is closed-not-merged in Gitea metadata (state=closed, merged=false, no merge commit), but the equivalent #51 content is present on master (landed via commit ec9ddb0 "docs: closed-not-merged PR reconciliation rules (#51)"). Verified on master (6089ec7): closed-not-merged/landed/reconciled definitions and direct-master-push restrictions in skills/llm-project-workflow/SKILL.md, and templates/reconcile-closed-not-merged-pr.md. No status:in-progress label present. Issue remains closed; no corrective PR needed.

Reconciliation: PR #52 is closed-not-merged in Gitea metadata (state=closed, merged=false, no merge commit), but the equivalent #51 content is present on `master` (landed via commit ec9ddb0 "docs: closed-not-merged PR reconciliation rules (#51)"). Verified on master (6089ec7): closed-not-merged/landed/reconciled definitions and direct-master-push restrictions in skills/llm-project-workflow/SKILL.md, and templates/reconcile-closed-not-merged-pr.md. No `status:in-progress` label present. Issue remains closed; no corrective PR needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
chore
documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 important
mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
read-only
Read-only, no mutation
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#51
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?