Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #2348
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Conflicts during rebase appends "conflicts" to commit message

By joseph.thom... on November 19, 2014 10:42 (imported from Google Code)


What steps will reproduce the problem?

  1. Rebase a change which will conflict
  2. Resolve the conflict
  3. Observe that the commit message has changed to include a list of the conflicts

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

The commit message should not be changed. This is how it is in vanilla Git, and how it was until very recently in TortoiseGit. A list of conflicts only really makes sense in a merge commit.

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

Windows 7 64-bit
TortoiseGit 1.8.11.0
msysgit 1.9.4.msysgit.2

Please provide any additional information below.

I use Gerrit, which requires that a "Change-Id" be appended to the commit message. I frequently forget to check the commit message and delete the conflicts list, and only realise when Gerrit rejects my commit for not having a Change-Id at the end. I then have to rebase again to amend the commit message.

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