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

Implement the pull-request and merge-request lifecycle #20

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 the pull-request/merge-request lifecycle through the common contract. An AI agent can create, inspect, list, comment on, and close requests, inspect diffs, and filter external requests according to repository policy.

Acceptance criteria

  • Pull request creation supports title, body, head, base, labels, and repository context where the provider supports them.
  • Pull request and GitLab merge request reads return normalized metadata, labels, comments/notes, author information, and diff access.
  • Request listing supports state and configured external-request filtering.
  • GitHub author associations and GitLab/Gitea membership or ownership data are mapped to the common external-request policy.
  • Unsupported author metadata produces an explicit capability result instead of an unsafe membership guess.
  • Request comments and close operations use the common contract.
  • GitHub, GitLab, and Gitea fake-CLI fixtures cover successful and unsupported lifecycle paths.

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 the pull-request/merge-request lifecycle through the common contract. An AI agent can create, inspect, list, comment on, and close requests, inspect diffs, and filter external requests according to repository policy. ## Acceptance criteria - [ ] Pull request creation supports title, body, head, base, labels, and repository context where the provider supports them. - [ ] Pull request and GitLab merge request reads return normalized metadata, labels, comments/notes, author information, and diff access. - [ ] Request listing supports state and configured external-request filtering. - [ ] GitHub author associations and GitLab/Gitea membership or ownership data are mapped to the common external-request policy. - [ ] Unsupported author metadata produces an explicit capability result instead of an unsafe membership guess. - [ ] Request comments and close operations use the common contract. - [ ] GitHub, GitLab, and Gitea fake-CLI fixtures cover successful and unsupported lifecycle paths. ## 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
#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
#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#20