Skip to content

v0.4.6

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 Nov 20:17
v0.4.6
1e23cfc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Added

  • why --json and the MCP tool why: commit.guard_would_block, the Git guard's
    verdict (its own identity check under [guard] on_mismatch, plus a trailer
    problem). commit.would_block stays the agent hook's verdict and is now
    documented as that.
  • setup -n --json: agents (per agent, hook and mcp as installed,
    plugin, missing or unavailable), uncovered and skills.
  • mcp install --agent copilot and setup --agent copilot register the gitpro MCP
    server for GitHub Copilot CLI in ~/.copilot/mcp-config.json (with
    --scope project, in the repo's .github/mcp.json). Copilot CLI still has no
    gitpro hook, so setup reports its hook as unavailable and exits 0 once the MCP
    entry is in place, as it does for Claude Desktop and opencode.
  • setup -n reports an installed gitpro skill (~/.claude/skills/gitpro,
    ~/.copilot/skills/gitpro, ~/.agents/skills/gitpro) that differs from the
    one in this gitpro, and setup -y updates only those copies, with a backup in
    gitpro's state folder (skill-backups/), not in the skills folder, and an undo
    line. It never creates a copy.
  • The skill (skills/gitpro/SKILL.md) is inside the wheel and the sdist.
  • Spec 23, docs/spec/23-agent-setup.md.

Changed

  • scan --fix --json without -y only previews, like -n, and prints
    "dry_run": true. 0.3 to 0.4.5 wrote without -y. Use -y; the VS Code
    extension already does.
  • setup --agent NAME for an agent gitpro cannot cover (Codex) prints a ✗ line
    and exits 1, in -n and in -y. setup --agent copilot does not: it registers
    the MCP server and the hook shows as unavailable. setup -n also exits 1 when an
    installed skill copy differs.
  • The skill: a rule set for committing, pushing and opening a pull request
    (check that gitpro is there, read commit.problems and not the exit code, a
    blocked commit is not done, push and PR fail closed), the missing deprecation
    rows (setup --write, scan --suggest), and corrected statements about
    setup, pins, uninstall, ambiguity and "read-only".

Fixed

  • A repo with no remote and no [default] name and email: the fix no longer
    offers gitpro setup --add PATH (there is no remote to learn from), and the
    text no longer says git will refuse to commit when git has its own email.
  • The MCP tool why returns the same error object as why --json (error,
    config: null, and the repo fields), with isError.

Get it

Assets 7
Loading