Milestones and issues

#Milestones

A task or an exploration can have a milestone. When you give intake a milestone, it writes it in the file. To see how far a milestone is, count its items by status. The panel shows a progress bar for each one.

#GitHub issues

scripts/sync-issues.mjs gives each task an issue in its first repository. A task takes part when its front matter has an issue: key, and an empty one creates the issue.

The issue gets the text of the task, a status: <status> label, and the milestone that issues.milestones of factory.json gives. It is closed when the task is done or discarded. The skills run the script after each change of status. A hub without the script has no issues.

{
  "issues": {
    "milestones": {
      "docs": "Docs",
      "billing": "Accounts and billing"
    }
  }
}

Edit the task in the hub, not the issue. The next sync replaces the text of the issue.

node scripts/sync-issues.mjs T-009      # these tasks
node scripts/sync-issues.mjs            # every task
node scripts/sync-issues.mjs --dry-run  # print what would change

An exploration has no issue.