You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(tools/mercurial): Mercurial (Hg) version-control support for the local dev-loop #601
Add tools/mercurial/ so the local dev-loop skills can operate on Mercurial (Hg) repositories, not just Git. Today the framework assumes Git everywhere — git checkout/commit/diff/rebase are baked directly into issue-fix-workflow, pr-management-code-review, and the setup-steward worktree machinery. This is the first "not only Git" version-control bridge and should establish the abstraction the others (SVN, Jujutsu, Fossil, Perforce) reuse.
Capabilities to provide (mirror the implicit Git contract the skills rely on):
History read: log, annotate/blame, file-at-revision (for the reproducer + reassess skills)
Patch/queue export for the fix-workflow hand-off (hg export, optionally MQ/evolve)
A thin VCS-capability shim so skills call vcs.diff / vcs.commit rather than git ... directly
Why: Mercurial still backs a meaningful slice of OSS — the Mercurial project itself, large historical Mozilla trees, Octobus/Heptapod (GitLab-on-Hg) hosting, Meta's internal Sapling lineage, and many academic / scientific repos. A project-agnostic stewardship framework that hard-codes Git can't be adopted by an Hg shop at all.
I have implemented a complete, possible approach for both Mercurial (hg) VCS backend support (#601) and the SourceHut (sr.ht) forge bridge (#607) in a fork and opened a pull request.
Closing as implemented. Mercurial support landed in #670 ("feat(tools/sourcehut, tools/vcs): add SourceHut forge bridge and implement Mercurial backend") and is on main.
Activity
feat(tools): add source-control (VCS) capability and wire it into git…
feat(tools): add source-control (VCS) capability and wire it into git…
feat(tools/vcs): implement the source-control (VCS) abstraction (#610)
feat(tools): require and document a Prerequisites section for every t…
onlyarnav commentedon Jul 1, 2026
Hi sir,
I have implemented a complete, possible approach for both Mercurial (
hg) VCS backend support (#601) and the SourceHut (sr.ht) forge bridge (#607) in a fork and opened a pull request.Here is a summary of the changes implemented:
tools/vcssupporting status, branch bookmarks, staging, commits, diffs, and worktree purges along with custom unit tests.tools/sourcehututilizing standard libraryurllibto handle GraphQL requests totodo.sr.ht(tickets, comments, status, labels),lists.sr.ht(mapping patchset emails to standard PR abstractions),builds.sr.ht(build statuses), andgit/hg.sr.htrepository metadata.Everything has been verified via unit tests and passes
skill-and-tool-validatechecks. Please kindly review the pull request!(Note: This implementation was built pair-programming using the Antigravity Gemini 3.5 Flash AI coding assistant).
justinmclean commentedon Jul 27, 2026
Closing as implemented. Mercurial support landed in #670 ("feat(tools/sourcehut, tools/vcs): add SourceHut forge bridge and implement Mercurial backend") and is on
main.