Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
TortoiseGit
TortoiseGit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 302
    • Issues 302
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 9
    • Merge requests 9
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #3461

Closed
Open
Created Nov 12, 2019 by Erik van der Gaag@erik.vandergaag

Performing refresh on Commit window loses new branch name

What steps will reproduce the problem?

  1. The current branch is on a merge commit
  2. Bring up the Commit window
  3. Check 'new branch' option and enter some text in the Edit input for a new branch name
  4. Press F5 to refresh modified files

What is the expected output? What do you see instead?

I expect that the new branch name I entered stays, but instead it gets cleared out.

What version of TortoiseGit and Git are you using? On what operating system?

TortoiseGit 2.9.0.0, version of git and OS are not relevant.

Please provide any additional information below.

This has been happening for a as long as I've been using TortoiseGit, but I've just now got around to filing a bug report for it.

Additional information by Yue Lin:
The new branch is cleared out by DDX:
(1) when the current branch is on a merge commit
image

(2) when cherry picking and conflict
image
image
(from https://git-scm.com/docs/git-cherry-pick) NOTE: Not sure how to reproduce this.

(3) when first commit in a init repo
image

(4) when using combine commit
image

Edited Nov 14, 2019 by Yue Lin Ho
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking