Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • hgitaly hgitaly
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • hgitalyhgitaly
  • Issues
  • #61

Closed
Open
Created May 26, 2021 by Georges Racinet@gracinet🦑Owner

CommitService: new methods for Mercurial specific changeset metadata

It would be a mistake to just add, e.g, branch and topic fields to the existing GitCommit message, hence to the responses of existing calls, because it would conflict with whatever upstream could add in the future.

Hence we should have either a separate method for Mercurial specific changeset information (branch, topic, phase etc.) or an aggregated one giving everything in one HgCommit message. The former would be a bit cheaper if that matters (probably not much at this stage)

Like #60, this is a fork of the protocol.

On the Rails side, this would allow to replace the hg subprocess call of HgGitRepository#hg_changeset_branch_topic by a HGitaly call.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking