check-milestones

Check and fix GitHub PR and issue milestones in brave-core.

3.5k|1.4k|Updated Nov 10, 2017
One-click install
npx skills add https://github.com/brave/brave-core --skill check-milestones-brave
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-milestones
Source: https://github.com/brave/brave-core/tree/main/.claude/skills/check-milestones
Command: npx skills add https://github.com/brave/brave-core --skill check-milestones-brave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that GitHub Pull Requests (PRs) and their associated issues have accurate and consistent milestones, streamlining the release process and improving project tracking.

Core Features & Use Cases

  • Automated Milestone Assignment: Correctly assigns milestones to PRs based on the branch they were merged into.
  • Issue Milestone Synchronization: Determines the appropriate milestone for issues based on the smallest version number where the fix has been merged, including uplifts.
  • Use Case: A developer merges a PR into the main branch. This Skill automatically assigns the 'Nightly' milestone to the PR and checks associated issues, updating their milestones if the fix was also uplifted to Beta or Release branches.

Quick Start

Run /check-milestones with a GitHub username to verify and fix milestones for recent PRs.

Frequently Asked Questions about check-milestones

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub PR and issue milestone synchronization?

You can automate GitHub milestone synchronization by running a command with a GitHub username to verify and fix milestones for recent PRs. The tool determines correct milestones based on merge branches and uplift status, ensuring alignment with release schedules.

How are issue milestones determined when PRs are uplifted to Beta or Release branches?

Issue milestones are determined by identifying the smallest version number where the fix has been merged. If a fix is uplifted to Beta or Release branches, the tool updates associated issues to reflect the appropriate release milestone accurately.

Do I need the GitHub CLI to check and fix repository milestones?

Yes, you need the GitHub CLI to check and fix repository milestones. The process also requires web fetching capabilities and parsing of release information from a specific wiki page to determine the correct release schedules.

What happens to PR milestones when a developer merges changes into the main branch?

When a developer merges changes into the main branch, the tool automatically assigns the 'Nightly' milestone to the PR. It then checks associated issues and updates their milestones if the fix was also uplifted to other branches.

Does this milestone checking process work for repositories other than brave-core?

The milestone checking process is specifically designed for the brave/brave-core repository. It parses release information from an associated wiki page to determine the correct milestones based on that specific project's release schedules.