FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Allowing Issues to continue safely after a PR
Using one-to-many Issue-to-PR and one-to-one branch-to-PR mappings with completion-based closure
Purpose
When an Issue contained multiple delivery stages, treating the first merged PR as completion could make remaining work untrackable.
Implementation
AGENTS.md changed the mapping to one Issue with multiple PRs and one branch per PR. A PR with unmet completion conditions must omit closing keywords and keep the Issue open; only the final PR with all conditions met closes it, and remaining work continues on a new branch.
- すべてのPRをIssueへ関連付けてください。IssueとPRは1対Nとし、1つのIssueに複数のPRを関連付けることができます。
- 作業ブランチとPRは1対1とし、同じIssueに複数のPRを作成する場合も、PRごとに別の作業ブランチを使用してください。
- 作業中にユーザーから追加要求があった場合は、ユーザーから別Issueを作成する明示的な指示がない限り、別Issueを作成せず、進行中のIssueのスコープを広げて対応してください。Rendering diagram…
What was confirmed
Verification results
The rules were checked across the three cases of an Issue with multiple PRs, unmet conditions, and all conditions met, and diff formatting passed.
No existing Issue state was changed as part of this Activity.
Basis for completion
The work was complete when PR completion was separated from Issue completion and remaining-work tracking and closure were tied to completion conditions.