-
Notifications
You must be signed in to change notification settings - Fork 575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge with empty commit changes commit message title #7573
Comments
Thanks a lot for reporting! I tried to reproduce the issue but failed. Screen.Recording.2025-03-11.at.11.18.01.movCould you have a look at the video and help me understand what went wrong when trying to reproduce the issue? Thank you. |
Hi @Byron , the new commit message looks correct on app UI, however after I push the combined commit to gitlab, the commit title is empty while the old commit title is in the folded "description" on gitlab pages. If I manually edit the combined commit message again, just "submit" the message dialog directly without change anything, the message will be correct on gitlab after force push the "newly edited" (save message directly without changing anything) commit. This issue only occurs in recent versions. ![]() |
Thanks, that's very helpful! My first hypothesis is that the UI may show something stale, so after creating a commit that would show up incorrectly in GitLab, but shows correctly in GitButler, could you hit To check whitespace, could you show the last line of this invocation (assuming the commit in question sits directly on a branch named
This would show the whitespace in the 'bad' state. ( Then, after editing the 'broken' commit in the UI, invoke the command again to show the 'good' state. I'd expect some difference in whitespace. After testing, I already noticed that GitButler leaves two newlines after the message title…
…while Git leaves only one if the body is empty.
Thanks again. |
On my device: |
Version
0.14.10
Operating System
Windows
Distribution Method
msi (Windows)
Describe the issue
See reproduce steps.
Reason for this action: to update the commit time to current time after add more changes to an existing commit.
How to reproduce (Optional)
Expected behavior (Optional)
Preserve the commit message title. (This was the behaviour prior 0.14.8 I think.)
Relevant log output (Optional)
The text was updated successfully, but these errors were encountered: