Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
thg
thg
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 788
    • Issues 788
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards

This instance will be upgraded to Heptapod 0.19.0rc2 on 2021-01-18 at 11:00 UTC+1 (a few minutes of downtime)

  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #3832

Closed
Open
Opened Jul 24, 2014 by Bitbucket Importer@bitbucket_importerOwner

Sync target is reset after detecting outgoing changesets

Created originally on Bitbucket by Anonymous

To reproduce:

  • Make a repository that has some bookmarks
  • Update to the tip of a bookmark, make some local changes
  • Open TortoiseHG Workbench
  • Click on the Synchronize button to bring up the sync UI
  • Click on the Target checkbox
  • Select your current tip as a revision in the drop list
  • Click 'Detect outgoing changesets'

Result: The target drop list is changed, and is now selecting the bookmark at the current revision, not the revision itself.

Expected Result: The target drop list should continue to have the revision selected, so that after inspecting you can push the changes, but not push the bookmark itself.

The motivation for this is that at our company, the "central" build repository is kept bookmark-free. Each team has staging repositories, where bookmarks are typically used to separate work for different projects and features. So when pushing upstream, it is important that the revision is pushed, not the bookmark. However the current UI always switches the dropdown to the bookmark, which means that the "review outgoing changesets" -> "push" workflow is error prone.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mercurial/tortoisehg/thg#3832