gabogg/hikcentral
Watch
1
0
Fork
You've already forked hikcentral
 0
Code Issues 113 Pull requests 8 Projects Releases Packages Wiki Activity Actions

docs(agents): group feature deliveries into milestones #179

Merged
gabogg merged 1 commit from docs/agents-milestones into master 2026-09-28 10:41:27 +00:00
Conversation 0 Commits 1 Files changed 5 +35 -1
gabogg commented 2026-09-28 10:34:40 +00:00
Owner
Copy link

Summary

Adds Forgejo milestones to the agent workflow, as an extra layer of order above triage labels. A milestone groups one feature delivery: the umbrella issue, its child issues, prerequisites pulled in to unblock it, and every PR that implements them.

  • New docs/agents/milestones.md covers:
    • When to create one: an umbrella split into two or more issues, or a delivery spanning two or more PRs.
    • Naming and description: titled by outcome; the description names the umbrella, spec and prerequisites.
    • Membership: children, review follow-ups, maintainer-declared prerequisites, PRs serving the feature, and items created by a scope split. A prerequisite already in another open milestone stays put, and the agent asks. Unrelated finds stay outside.
    • Closing: close the milestone when every item is closed, and note it on the umbrella.
  • AGENTS.md gets a short pointer; docs/README.md indexes the new doc.
  • forgejo-cli.md gains the tea commands for creating milestones, assigning them (at creation or later) and listing their items.
  • The PR protocol in git-and-workflow.md adds a step: a PR takes the milestone of the issue it closes.

The first milestone, Historical passenger-flow backfill, already exists and holds 18 items:

Architectural impact

None; this changes documentation and workflow only.

Verification

  • python3 scripts/check_docs.py passes.
  • The documented tea commands were run against the new milestone (milestones create, milestones issues add, issues list --milestones, pr list --fields index,title,milestone).

Checklist

  • Milestone rules, commands and pointers.
  • Review passes per docs/standards/git-and-workflow.md.

🤖 Generated with Claude Code

## Summary Adds Forgejo **milestones** to the agent workflow, as an extra layer of order above triage labels. A milestone groups one feature delivery: the umbrella issue, its child issues, prerequisites pulled in to unblock it, and every PR that implements them. - New `docs/agents/milestones.md` covers: - **When to create one:** an umbrella split into two or more issues, or a delivery spanning two or more PRs. - **Naming and description:** titled by outcome; the description names the umbrella, spec and prerequisites. - **Membership:** children, review follow-ups, maintainer-declared prerequisites, PRs serving the feature, and items created by a scope split. A prerequisite already in another open milestone stays put, and the agent asks. Unrelated finds stay outside. - **Closing:** close the milestone when every item is closed, and note it on the umbrella. - `AGENTS.md` gets a short pointer; `docs/README.md` indexes the new doc. - `forgejo-cli.md` gains the `tea` commands for creating milestones, assigning them (at creation or later) and listing their items. - The PR protocol in `git-and-workflow.md` adds a step: a PR takes the milestone of the issue it closes. The first milestone, **Historical passenger-flow backfill**, already exists and holds 18 items: - Issues #160, #162–#165, plus the prerequisites #108, #113, #114 and #161. - PRs #166, #170–#173 and #175–#178. ## Architectural impact None; this changes documentation and workflow only. ## Verification - [x] `python3 scripts/check_docs.py` passes. - [x] The documented `tea` commands were run against the new milestone (`milestones create`, `milestones issues add`, `issues list --milestones`, `pr list --fields index,title,milestone`). ## Checklist - [x] Milestone rules, commands and pointers. - [x] Review passes per `docs/standards/git-and-workflow.md`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs(agents): group feature deliveries into milestones
All checks were successful
CI / lint-and-test (pull_request) Successful in 2m8s
Details
b0bef9dde3 
Define when to create a Forgejo milestone (an umbrella split into two or
more issues, or a delivery spanning two or more PRs), how to name and
describe it, which issues and PRs join it (children, review follow-ups,
maintainer-declared prerequisites, feature-serving PRs, split scope), what
stays out, and when to close it. Add tea commands, an AGENTS.md pointer, a
docs index entry and the PR-protocol step that assigns a PR its issue's
milestone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gabogg changed title from WIP: docs(agents): group feature deliveries into milestones to docs(agents): group feature deliveries into milestones 2026-09-28 10:41:19 +00:00
gabogg merged commit 277aaeb2b5 into master 2026-09-28 10:41:27 +00:00
gabogg deleted branch docs/agents-milestones 2026-09-28 10:41:27 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
blocked
Waits on the issues listed in its "Blocked by:" line before implementation

  
bug
Category: something is broken; behaviour differs from the spec or docs

  
enhancement
Category: new feature or improvement, including refactors, chores and docs

  
high-priority
Address before ordinary-priority work; independent of triage readiness and blockers

  
low-priority
Address after ordinary-priority work; independent of triage readiness and blockers

  
needs-info
Waiting on reporter for more information

  
needs-triage
Maintainer needs to evaluate this issue

  
ready-for-agent
Fully specified, ready for an AFK agent

  
ready-for-human
Requires human implementation

  
referenced
Previously closed issue reopened or referenced by an open issue; visible history marker

  
research
Needs investigation (internet or local resources) before it can be triaged down; used alongside a category and a triage role

  
wontfix
Will not be actioned

No labels
blocked
bug
enhancement
high-priority
low-priority
needs-info
needs-triage
ready-for-agent
ready-for-human
referenced
research
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gabogg/hikcentral!179
No description provided.