Repository navigation
Releases
v0.12.2
v0.12.1
v0.12.0
Fixes #72. Consumer: pr-reviewer-plugin#367.
Change
gh_issue.scoped_default_repo(repo): a context manager over aContextVar;gh_issue.scoped_default()reads it.resolve_repo: explicitrepo> scoped default > configured default >GITHUB_DEFAULT_REPO/GH_REPO. Every tool resolves through it, so all read / write / review / release tools honour the scope.- An explicit repo still wins (so a caller's own guard still sees a call that names the wrong repo); an empty or malformed scope changes nothing; nesting restores the outer scope on exit.
- PROTO.md §6 documents the new precedence.
- Version 0.11.0 → 0.12.0 (manifest, pyproject, uv.lock).
Why
Vera runs review rounds across 170 repos with default_repo: "", so an omitted repo resolves to github.repos[0] = protoAgent. On mythxengine#966 a finder lane read protoAgent's CHANGELOG.md / pyproject.toml that way (pr-reviewer-plugin#367). The pr-reviewer will wrap each round in scoped_default_repo(round_repo).
Verification
Tests: precedence (scope beats configured default, explicit beats scope, nested scopes restore), malformed scopes are ignored, the scope follows asyncio tasks started inside it and not ones outside, and github_get_pr without repo targets the scoped repo inside the scope and the configured one after. ruff (0.15.10 pin) + pytest: 579 passed, 13 skipped.
🤖 Generated with Claude Code
v0.11.0
This release adds count badges to the GitHub board and improves failure context in run logs and review threads.
GitHub Board
- Issues and PRs tabs display count badges sourced from a new
/countsdata route. - The board and drawer adopt plugin-kit primitives (pl-tabs, pl-badge, pl-prose, pl-dot, pl-link, pl-iconbtn) and use real status tokens.
Failure and Review Context
github_run_failurepreserves context lines before each matched error and supports an optional grep filter.github_review_threadsstrips CodeRabbit boilerplate before applying character caps and accepts abody_max_charsparameter.
v0.10.1
v0.10.1 makes the GitHub tools cheaper to carry on every model call. It changes text only.
Token efficiency (#58)
- All 38
github_*tool descriptions are each rewritten as one short paragraph: what the tool does, when to use it instead of a sibling, and the hard rules that apply when calling it. Schema size drops by about 43% for an agent withgithub.write: true. - The repeated "Repository as owner/name…" line, the
Args:/Returns:blocks, and the 8-space docstring indentation no longer ship in every description. - Workflow guidance (PR review order, fix-round thread replies, CI triage, filing, merging, the release sequence) moves to a new
skills/github/SKILL.md, which the host loads automatically. - No tool was renamed. No parameter, type, default, required flag or behavior changed.
v0.10.0
Release notes for v0.10.0 focus on new GitHub release tooling and significant UI enhancements for viewing pull requests and issues.
GitHub Release Tooling
- Agents can now cut a tagged release end to end using new tools:
github_dispatch_workflow,github_create_tag,github_edit_release, andgithub_upload_release_asset. github_create_tagcreates an annotated tag at an exact commit, checks the version inpyproject.tomlfirst, and refuses to move an existing tag.github_merge_praccepts ashaparameter to pin the REST merge to the verified head; it returns a 409 and refuses if the head has changed.github_upload_release_assetuploads text using the exact asset name; it does not support thepath#labelsyntax, which only sets a label.- New read tools
github_run_jobs,github_release, andgithub_release_assetprovide per-job status, release metadata, and small asset text. github_get_prnow returns the head SHA and, once merged, the merge commit.
GitHub View: PR Drawer
- The PR drawer now includes a shell with a full-width GitHub rail view.
- The "Checks" and "Files" tabs display CI status (including failure log tails) and per-file diffs.
- The "Conversation" tab displays PR comments and full review threads.
GitHub View: Issues and List
- An issue drawer displays the issue body, comments, labels, assignees, and linked PRs.
- The GitHub view list includes a search box, a "load more" control for past the first 30 items, and a CI rollup chip on PR rows.
v0.9.3
Pull Request Merging
github_merge_prnow accepts optionalsubjectandbodyarguments to customize the merge commit message usinggh pr merge --subjectand--body.- Passing these arguments to a rebase merge is refused outright.
- The customized message is visible in dry run output.
v0.9.2
v0.9.2 adds new GitHub tools and improves data visibility for pull requests and issues.
GitHub Integrations
github_get_prandgithub_get_issuenow return the full body text, indicating truncation with a[truncated: N of M chars]marker when the content exceeds limits.github_edit_issueallows updating issue titles and bodies.github_create_labelenables the creation of new labels.
v0.9.1
v0.9.0
GitHub Review Threads
- The agent can now list, reply to, and resolve individual PR review threads, clearing the "auto-merge pending" status on board cards after a fix round.
- New tools:
github_review_threads(read),github_reply_thread(write), andgithub_resolve_thread(write). - Thread IDs are validated before execution, and GraphQL errors surface as
Errorstrings.
Error Handling
github_read_fileandgithub_read_pr_filenow probe up to four parent directories on a 404 to distinguish between an invalid path and an invalid repository/ref.- If a parent directory exists, the error clarifies that the repo and ref are valid but the path is wrong, and lists up to 60 entries from that directory.
fetch_issuesnow rejectsstate="merged"with the documented message, as issues do not have a merged state; PRs remain unaffected.