Escape # character in a redirect error message

After doing the interactive redirect in git, I want to have a commit message that starts with the # character (hash or pound), but lines starting with # are treated as comments and are ignored.

Is there a way to escape the # character so that my transfer message really starts with # ?

More details

I am performing an interactive reboot using:

 git rebase -i HEAD~4 

Then in the editor I do everything that is necessary, for example:

 pick b010299 #91691 Add test for logging in with valid credentials reword 5e9159d 91691 Implement log-in feature pick 2735aa3 #91691 Re-factor logic pick 14bd500 #91691 Tidy up 'using' declarations # Rebase 60d6e3f..14bd500 onto 60d6e3f # # Commands: # p, pick = use commit # r, reword = use commit, but edit the commit message # e, edit = use commit, but stop for amending # s, squash = use commit, but meld into previous commit # f, fixup = like "squash", but discard this commit log message # x, exec = run command (the rest of the line) using shell # # These lines can be re-ordered; they are executed from top to bottom. # # If you remove a line here THAT COMMIT WILL BE LOST. # # However, if you remove everything, the rebase will be aborted. # # Note that empty commits are commented out 

Then git loads the commit message in my text editor for the commit that I want to rewrite, but I want to save the commit message with # at the beginning:

 #91691 Implement log-in feature # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # rebase in progress; onto 60d6e3f # You are currently editing a commit while rebasing branch 'master' on '60d6e3f'. # # Changes to be committed: # modified: My.Website.LogInController.cs 

But that means my commit message will be ignored. How do I make a commit #91691 Implement log-in feature message?

+5
source share
1 answer

If you save the message with the message # , then your commit message is empty (you can also delete everything in the message), git will show you what to do:

 Aborting commit due to empty commit message. Could not amend commit after successfully picking 5e9159d9ce3a5c3c87a4fb7932fda4e53c7891db... 91691 Implement log-in feature This is most likely due to an empty commit message, or the pre-commit hook failed. If the pre-commit hook failed, you may need to resolve the issue before you are able to reword the commit. You can amend the commit now, with git commit --amend Once you are satisfied with your changes, run git rebase --continue 

So just change the message:

 git commit --amend -m "#91691 Implement log-in feature" 

and continue rebase:

 git rebase --continue 
+9
source

Source: https://habr.com/ru/post/1241506/


All Articles