Repository navigation
pr acceptance tracking
Keep acceptance criteria and tracking links accurate when creating or updating GitHub and Azure DevOps pull requests.
| Type | Issue |
|---|---|
| Parent | Issue #103 |
| Sub-issue | Issue #104 |
| Sub-issue | Issue #105 |
PRs may be linked while verified acceptance checklist items remain unchecked. Completion must be based on evidence for each criterion.
Improve the existing PR skills and the Azure Boards handoff. Read each relevant issue or work item, map criteria to implementation and verification evidence, update only verified completed checklist entries while preserving unrelated content, and read back changes. Leave incomplete or unverified criteria open. Ensure and verify PR links. Do not treat checklist updates as authorization to close an issue or transition a work item.
For lengthy GitHub issue details or richer records, require issue artifacts for supporting research, designs, plans, or visualizations. Keep the issue summary and acceptance criteria in the issue body, link to the artifact, and continue the approved Wiki publication. If artifact creation or verification is unavailable, report the required work as incomplete rather than silently omitting it.
- Update GitHub PR acceptance criteria and issue linkage guidance.
- Update Azure Repos and Boards guidance for work item criteria and PR linkage.
- Synchronize applicable mirrors, bilingual documentation, and metadata.
- Add GitHub issue artifact creation, discovery, updates, and verification to the issue workflow and acceptance review.
Validate skill metadata and repository checks, and exercise partial completion, missing evidence, and multiple tracking items with realistic isolated scenarios. Distinguish static or simulated verification from live service verification.