Skip to content

feat(tools/mercurial): Mercurial (Hg) version-control support for the local dev-loop #601

Closed

Description

@potiuk

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):

  • Working-copy ops: branch/bookmark create + switch, commit, hg diff, hg status
  • 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.

Reference:

Activity

  1. added
    enhancementNew feature or request
    capability:platformFramework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)
    source control systemVersion control systems and the forges/services that host them
    on Jun 28, 2026
  2. onlyarnav commented on Jul 1, 2026

    @onlyarnav
    Member

    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:

    Everything has been verified via unit tests and passes skill-and-tool-validate checks. Please kindly review the pull request!

    (Note: This implementation was built pair-programming using the Antigravity Gemini 3.5 Flash AI coding assistant).

  3. justinmclean commented on Jul 27, 2026

    @justinmclean
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    capability:platformFramework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)enhancementNew feature or requestfamily:toolstools/*good first issueGood for newcomerssource control systemVersion control systems and the forges/services that host them

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions