![\"\"](\"https:\/\/www.scmgalaxy.com\/tutorials\/wp-content\/uploads\/2018\/08\/git-1.png\")
<\/p>\n<\/p>\n
Best practice says that before you commit in git, you need to either do git pull or git fetch\/merge. However, there is a way to find out wheather your branches is not in sync with remote.<\/p>\n
To check the remote repo status you are really simulating a “fetch”<\/strong> To bring your remote refs up to date<\/strong> This command will print whether the branch you are tracking is ahead, behind or has diverged with remote. If it says nothing, the local and remote are the same.<\/strong> To pull<\/strong> Compare the two branches:<\/strong> Best practice says that before you commit in git, you need to either do git pull or git fetch\/merge. However, […]<\/p>\n","protected":false},"author":4,"featured_media":5277,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[38],"tags":[160,5020,5017,5021,5018,5019,5022],"class_list":["post-5222","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-git","tag-git","tag-git-commit","tag-git-fetch","tag-git-merge","tag-git-pull","tag-git-push","tag-git-remote"],"yoast_head":"\n
\n$ git fetch -v –dry-run<\/p>\n
\n$ git remote -v update<\/p>\n
\n$ git status -uno<\/p>\n
\n$ git pull origin <<branchname>>
\nor
\n$ git fetch origin <<branchname>>
\n$ git merge remote\/<<branchname>>
\n$ git commit<\/p>\n
\n$ git log HEAD..origin\/master –oneline<\/p>\n","protected":false},"excerpt":{"rendered":"