|
Hello to all! I have a small issue with git-gui. I added the git-bugreport to the attachement. Warm regards, Lauri Reilson • Software
Engineer PROEKSPERT • Sõpruse
pst 157, 13417 Tallinn, Estonia, EU |
Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) Added files for commiting using git-gui. Provided one line commit message Whatd did you expect to happen? (Expected behavior) Expected to commit using git-gui. Commit message was in the format <#task-id message>. I use ";" instead of comment symbol as "#" is used as a means to track task id. What happened instead? (Actual behavior) Git-gui gave error message, that I need to provide commit message. Tried one line, folled the error message (first line, blank line, remaining lines). Also, when ammending, git-gui messed up the message. Message was in the form of: #123456 message <blank line> - Some small description And git-gui turned this into: - Some small description What's different between what you expected and what actually happened? Commit message not being what I wrote and not being able to commit. Anything else you want to add: Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.49.0.windows.1 cpu: x86_64 sizeof-long: 4 sizeof-size_t: 8 shell-path: D:/git-sdk-64-build-installers/usr/bin/sh feature: fsmonitor--daemon libcurl: 8.12.1 OpenSSL: OpenSSL 3.2.4 11 Feb 2025 zlib: 1.3.1 uname: Windows 10.0 26100 compiler info: gnuc: 14.2, msvc libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks]
