![]() ![]() That means git status -porcelain keep displaying a different result than git status, this time because of the lack of translation.īut that output is now always the same (independent of the LOCALE used for the translation, since said translation is now deactivated by the -porcelain option)Īnd git status -porcelain is improved again in Git 2.13 (Q2 2017) Translation for " git status -short" which is essentially the same, but Use hardcoded strings when -porcelain is used, but keep the gettext (ahead, behind, gone), and used gettext to translate the string. " git status -branch -porcelain" displays the status of the branch Note: git status -porcelain has just been made a bit more reliable with commit 7a76c28, for git 1.9.2 (April 2014), by Matthieu Moy moy) disable translation when -porcelain is used Would it be ok, in the long run, to rely on git log, or should I use a "plumbing" command instead? If [ $(git status -porcelain | wc -l) != "0" \ So my question is: what do I need to add to the original script to also identify when the repo has unpushed changes? In particular, would this be a correct approach? #!/bin/bash Nothing to commit, working directory clean # (use "git push" to publish your local commits) # Your branch is ahead of 'origin/master' by 1 commit. ![]() Here is an example math-hl]$ git status math-hl]$ git status In particular, git status will report unpushed changes, while git status -porcelain will not. Unfortunately git status -porcelain and git status do not do exactly the same thing. The idea behind that answer was to emulate what the programmer would do: run git status and then examine the output. The answer I adopted from that discussion was the following: #!/bin/sh An earlier question resulted in some ideas on how to check whether your Git repo contains a dirty index or untracked files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |