You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[work-item-creation] Work items not consistently receiving required labels #38
Added required-metadata preflight, missing GitHub label-definition creation, Azure DevOps System.Tags handling, and readback after item creation. Repairs preserve additional metadata, persistent failures stop the batch with existing IDs, and retries reuse created items. Aligned platform formats and creator tools, and routed planning proposals through the shared creation checks.
Validation: git diff --check and npm --prefix docs run build passed. Independent instruction review covered missing labels, repair failures, ADO required tags, and standalone proposal intake with no remaining significant findings. No test work items were created.
Changes are committed and pushed. Merge the dependency first: #78. Retarget this PR to main if GitHub has not done so automatically. The issue remains open until merge.
Activity
fedeoliv commentedon Oct 16, 2026
Implementation verified, pending merge.
Added required-metadata preflight, missing GitHub label-definition creation, Azure DevOps System.Tags handling, and readback after item creation. Repairs preserve additional metadata, persistent failures stop the batch with existing IDs, and retries reuse created items. Aligned platform formats and creator tools, and routed planning proposals through the shared creation checks.
Validation:
git diff --checkandnpm --prefix docs run buildpassed. Independent instruction review covered missing labels, repair failures, ADO required tags, and standalone proposal intake with no remaining significant findings. No test work items were created.Branch:
feature/38-required-work-item-labels.Commit:
65e0eaf5bf99bdf7998c996f9fcf5b2a71cfae4e.PR: #79.
Changes are committed and pushed. Merge the dependency first: #78. Retarget this PR to main if GitHub has not done so automatically. The issue remains open until merge.