# [RFC] git subcommand to check if branch is up-to-date with upstream 4 messages from 2016-07-25 to 2016-07-26. Participants: Sidhant Sharma, Junio C Hamano, Jakub Narębski. Thread: https://gitlist.dev/t/42919 ## Sidhant Sharma, 2016-07-25 12:58 Subject: [RFC] git subcommand to check if branch is up-to-date with upstream Message-ID: <57960CFF.5060104@gmail.com> URL: https://gitlist.dev/e/57960CFF.5060104%40gmail.com ``` Hi, I was wondering if it would be a good idea to have a command to check if a push or pull is required. Perhaps it can also suggest if changes are fast-forward or the branches (local and remote) have diverged. The reason I feel the need of such a command is when I need to check if my branch is up-to-date with the remote, and when I need to know if my local has diverged. Currently I use a script based on this stackoverflow answer[1] Not an extremely useful tool, but I thought it'll be good to have it. Warm regards, Sidhant Sharma [1] http://stackoverflow.com/a/3278427/5211579 ``` ## Junio C Hamano, 2016-07-25 16:58 Subject: Re: [RFC] git subcommand to check if branch is up-to-date with upstream Message-ID: URL: https://gitlist.dev/e/xmqqd1m17iyb.fsf%40gitster.mtv.corp.google.com In-Reply-To: <57960CFF.5060104@gmail.com> ``` Sidhant Sharma writes: > I was wondering if it would be a good idea to have a command to check if a > push or pull is required. Perhaps it can also suggest if changes are > fast-forward or the branches (local and remote) have diverged. Doesn't "branch -v" give that information these days? You'd need to "fetch" first to get the up-to-date worldview before running it, of course. ``` ## Jakub Narębski, 2016-07-25 17:33 Subject: Re: [RFC] git subcommand to check if branch is up-to-date with upstream Message-ID: <57964D7F.90402@gmail.com> URL: https://gitlist.dev/e/57964D7F.90402%40gmail.com In-Reply-To: ``` W dniu 2016-07-25 o 18:58, Junio C Hamano pisze: > Sidhant Sharma writes: > >> I was wondering if it would be a good idea to have a command to check if a >> push or pull is required. Perhaps it can also suggest if changes are >> fast-forward or the branches (local and remote) have diverged. > > Doesn't "branch -v" give that information these days? You'd need to > "fetch" first to get the up-to-date worldview before running it, of > course. You need "branch -v -v". For current branch, you can simply run "git checkout". All this is the information for end user, not scripts. $ git branch -v -v * gitweb-docs 4ebf58d [origin/master: ahead 1] gitweb(1): Document query parameters master 08bb350 [origin/master] Sixth batch of topics for 2.10 $ git checkout Your branch is ahead of 'origin/master' by 1 commit. (use "git push" to publish your local commits) -- Jakub Narębski ``` ## Sidhant Sharma, 2016-07-26 09:32 Subject: Re: [RFC] git subcommand to check if branch is up-to-date with upstream Message-ID: <57972E10.4020403@gmail.com> URL: https://gitlist.dev/e/57972E10.4020403%40gmail.com In-Reply-To: <57964D7F.90402@gmail.com> ``` On Monday 25 July 2016 11:03 PM, Jakub Narębski wrote: > W dniu 2016-07-25 o 18:58, Junio C Hamano pisze: >> Sidhant Sharma writes: >> >>> I was wondering if it would be a good idea to have a command to check if a >>> push or pull is required. Perhaps it can also suggest if changes are >>> fast-forward or the branches (local and remote) have diverged. >> Doesn't "branch -v" give that information these days? You'd need to >> "fetch" first to get the up-to-date worldview before running it, of >> course. > You need "branch -v -v". For current branch, you can simply run "git checkout". > All this is the information for end user, not scripts. > > $ git branch -v -v > * gitweb-docs 4ebf58d [origin/master: ahead 1] gitweb(1): Document query parameters > master 08bb350 [origin/master] Sixth batch of topics for 2.10 > > $ git checkout > Your branch is ahead of 'origin/master' by 1 commit. > (use "git push" to publish your local commits) > Nice, didn't know that one. Thanks for the tip. Regards, Sidhant Sharma ```