Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 839
    • Issues 839
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurialmercurial
  • TortoiseHgTortoiseHg
  • thgthg
  • Issues
  • #3822
Closed
Open
Issue created Jul 15, 2014 by Bitbucket Importer@bitbucket_importerOwner

cannot graft to a newly created named branch

Created originally on Bitbucket by afriza (Afriza N. Arief)

a workflow described in http://draketo.de/light/english/mercurial/complete-branching-strategy#graft-releases

You have changes 1, 2, 3, 4 and 5 on default. First you want to create a release which contains 1 and 4, but not 2, 3 or 5.

#!bash

hg update 1
hg branch stable
hg graft 4

Steps:

  • update to 1 via GUI
  • create stable branch from option in commit widget or hg branch <new-branch>
  • graft 4 via GUI

Expected:

  • created a new branch named stable containing grafted 4 with 1 as parent

Actual:

  • branch creation is detected as changes that needs to be discarded
  • once discarded, 4 is grafted into default branch with 1 as parent
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking