Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg-hgtk thg-hgtk
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 519
    • Issues 519
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thg-hgtkthg-hgtk
  • Issues
  • #1646

Closed
Open
Created Dec 03, 2010 by Bitbucket Importer@bitbucket_importerOwner

Close Branch commit with unticked changes still commits changes

Created originally on Bitbucket by willfarb

To reproduce:

Start: Have a working copy with some changes to files which are as-yet uncommitted. Be working on a named branch.

Open the Commit GUI.

Unselect ALL the changes, so that there are no changes to be made.

Click on the 'branch: branchname' button, and select 'Close named branch'.

Click commit.

Now, to see the issue:

Open Repository Explorer (or refresh).

Note that the most recent commit includes the deselected changes.

Current workaround:

Shelve or revert any changes before trying to close named branch.

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