steve/skills
Public Access
1
0
Fork 0
Code Issues 11 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Implement idempotent labels and assignment #19

New Issue
Open
opened 2026-08-17 22:01:07 -04:00 by steve · 0 comments
steve commented 2026-08-17 22:01:07 -04:00
Owner
Copy Link
Copy Source

Part of Provider-neutral tracker automation CLI and library

Parent

Provider-neutral tracker automation CLI and library

What to build

Deliver idempotent label and assignment operations. An AI agent can ensure a label exists, apply or remove it, and assign an issue or request without exploratory existence queries or provider-specific syntax.

Acceptance criteria

  • Missing labels are created automatically before they are applied on every supported provider.
  • Existing label metadata is preserved unless an explicit update is requested.
  • Newly created labels receive deterministic defaults.
  • Adding an existing label, ensuring an existing label, repeating assignment, and repeating claim are safe operations.
  • Labels can be added to or removed from issues and pull requests/merge requests.
  • Assignment supports the current authenticated user and explicit users where the provider permits it.
  • Existing-label, missing-label, metadata-mismatch, assignment-failure, and replay tests cover all providers.

Blocked by

Part of [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## Parent [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## What to build Deliver idempotent label and assignment operations. An AI agent can ensure a label exists, apply or remove it, and assign an issue or request without exploratory existence queries or provider-specific syntax. ## Acceptance criteria - [ ] Missing labels are created automatically before they are applied on every supported provider. - [ ] Existing label metadata is preserved unless an explicit update is requested. - [ ] Newly created labels receive deterministic defaults. - [ ] Adding an existing label, ensuring an existing label, repeating assignment, and repeating claim are safe operations. - [ ] Labels can be added to or removed from issues and pull requests/merge requests. - [ ] Assignment supports the current authenticated user and explicit users where the provider permits it. - [ ] Existing-label, missing-label, metadata-mismatch, assignment-failure, and replay tests cover all providers. ## Blocked by - [Bootstrap the tracker runtime and provider selection](http://gitea.sagacity.ca/steve/skills/issues/17)
steve added the ready-for-agent label 2026-08-17 22:01:07 -04:00
steve added a new dependency 2026-08-17 22:02:10 -04:00
#17 Bootstrap the tracker runtime and provider selection
steve added a new dependency 2026-08-17 22:02:10 -04:00
#21 Implement wayfinding maps and child tickets
steve added a new dependency 2026-08-17 22:02:10 -04:00
#24 Harden cross-provider behavior and migrate skills
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
in-progress
in-review
needs-info
needs-review
Waiting for review by a human
 needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
Wayfinder human decision ticket
 wayfinder:map
Wayfinder decision map
 wontfix
No labels ready-for-agent
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
steve (Steve Beaulac)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#21 Implement wayfinding maps and child tickets
steve/skills
#24 Harden cross-provider behavior and migrate skills
steve/skills
Depends on
#17 Bootstrap the tracker runtime and provider selection
steve/skills
Reference: steve/skills#19