init-milestones

You can automate GitHub milestones setup by running an initialization script that detects version baselines from v* tags or package.json and creates general backlog, line, and next release milestones via the GitHub API.

Yes, you need the GitHub CLI (gh) along with Git and Node.js installed. The script uses these dependencies to detect version baselines from v* tags or package.json and to create or update milestones via the GitHub API.

Yes, you can enable an optional history mode to process tag-based milestones. This mode generates milestones from vX.Y.Z tags, handling both open and closed states, while enforcing idempotency across multiple runs.

The best way to manage major.minor.x line milestones is to use an automation script that detects your current version baseline and automatically creates corresponding line milestones alongside a major.minor.next release target.

Milestone creation should not duplicate entries because the script enforces idempotency via milestone titles. If duplicates appear, ensure the script successfully matched existing milestone titles during its GitHub API update checks.

Yes, the tool works without a package.json file by falling back to detect version baselines from v* tags in your Git history. It uses Node.js and Git to establish the baseline for creating your repository milestones.