Usually it is always at the tip or the HEAD i.e. The asterik * that is the HEAD of my local branch or at which commit on that branch I am on. The -all option will also display your local & your "remotes" Master is my current main branch which I push my changes to from my local repo. Over here bitbucketFrmWin is my alias for my remote bitbucket repoĪsOf16Jan2018 is a branch that I am no longer interested Remotes/bitbucketFrmWin/master 58470cd This is really crazy - Spent more than a week - Singleton still gives * CurrAsOf18Jan2018 50d1fc6 Pedantic but done - gitNotes.txt In steps 4 & 5 you will have to use a userId and passWord to interact with your remote repo on (6) git statusįrom now on git status will actually tell you whether you are behind or ahead of your remote github repo because of the -track (ing) option you had done in your pushĪnother useful command to use from this point onwards will be git branch -vv -all The -u is the same as -track which means that your local branch positioned HEAD will be tracking the master branch at your remote alias myGitHubOrBitBucketRep This command will push your committed changes (aka snap shots in git speak) to YourGitAppRepo.git on onto the master branch and if master on your remote repo is not ahead of your local branch and it is just a couple of commits behind - will accept this push But I have been using specific alias branch names which in your case is "myGitHubOrBitBucketRepo" (5) git push -u myGitHubOrBitBucketRepo HEAD:master Usually the default name for your remote repo on github is given as "origin".
(4) git remote add myGitHubOrBitBucketRepo You need to commit whatever changes yout want to keep - locally before you can "push" your changes to your github repo remotely ie only after you have told git where your remote git repo is. Works in Windows if use the Windows git-bash.exe It uses mingW64 emulator to simulate linux environment. (b) Some more details and do not forget to put closing quote mark" (a) Continue typing more comments which are detailed if necessary (3) git commit -m "A Nice Subject line for many file commits In fact git will hint to you what it thinks is the next step in your work flow (2) git add Will always tell you what is uncommitted and what needs to be "added" (staged) for committing to your local repo.
Your work flow for ensuring that your changes are added correctly to your remote github repo in "normal" cases should follow these stages.
0 kommentar(er)
