Origin master

Anotações:

• The github remote repository. Where all the code is stored and where all the local users that are collaborators are pushing code and pulling code from. It comes by default with a master branch, and in order to have access to it you must put *git remote add origin * so you can start pushing and pulling from there.It may contains also branches but these are not downloaded automatically.

1. Jake's local master

   Anotações:

   • The master branch of your local git repo. It comes natively once you type git init.  From this place you can interact with other local branches and also with the remote master via pulling and pushing. Important Note: Always inform your colleagues before touching the master, applying changes to it, rewritting history or updating the state with new changes via pull and push.
   1. Jake's local branch

      Anotações:

      • Here the user an experiment freely as he pleases. Play with features, rewrite history without fear and test new stuff to see if it works.  In order to save his code, the programmer can push his code either to master remote branch (not recommended at all!!!) or to a remote branch that will be created on github.  The latter can also be done automatically when during the first push and while in branch the user types *git push --set-upstream origin .  After the first push, you can type just git push and automatically git finds it's way to remote repository.
      1. Jake's origin branch

         Anotações:

         • One of the remote branches.  Exactly like local branches those branches are copies of the master branch of the remote repository.  People who have created branches into their own computers can freely interact with those remote branches in order to have a safe place to push code there and make progress to their code without even touching the master neither locally nor in remote.
2. Mauro's local master

   Anotações:

   • The master branch of your local git repo. It comes natively once you type git init. 
   1. Mauro's local branch

      Anotações:

      • Here the user an experiment freely as he pleases. Play with features, rewrite history without fear and test new stuff to see if it works.  In order to save his code, the programmer can push his code either to master remote branch (not recommended at all!!!) or to a remote branch that will be created on github.  The latter can also be done automatically when during the first push and while in branch the user types *git push --set-upstream origin .  After the first push, you can type just git push and automatically git finds it's way to remote repository.
      1. Mauro's origin branch

         Anotações:

         • One of the remote branches.  Exactly like local branches those branches are copies of the master branch of the remote repository.  People who have created branches into their own computers can freely interact with those remote branches in order to have a safe place to push code there and make progress to their code without even touching the master neither locally nor in remote.
3. Meir's local master

   Anotações:

   • The master branch of your local git repo. It comes natively once you type git init. 
   1. Meir's local branch

      Anotações:

      • Here the user an experiment freely as he pleases. Play with features, rewrite history without fear and test new stuff to see if it works.  In order to save his code, the programmer can push his code either to master remote branch (not recommended at all!!!) or to a remote branch that will be created on github.  The latter can also be done automatically when during the first push and while in branch the user types *git push --set-upstream origin .  After the first push, you can type just git push and automatically git finds it's way to remote repository.
      1. Meir's origin branch

         Anotações:

         • One of the remote branches.  Exactly like local branches those branches are copies of the master branch of the remote repository.  People who have created branches into their own computers can freely interact with those remote branches in order to have a safe place to push code there and make progress to their code without even touching the master neither locally nor in remote.