Git Workflow - Tutorial
- Create an oranization.
- Create a project inside the organization.
- If the project is private you need to add all the collaborators.
- Each collaborator has to fork to the machine.
- Every developer has to clone their project to their machine.
- The programmer has to add the remotes of the original project.
- It must make sure that everything is correctly synced.
- A new branch will be created to work with a feature.
- Once the work is done, the developer pushes his changes to his fork.
- On Github will show up an option to create a pull request.
- Once the pull request is created the project manager will check it out.
- The pull request either is rejected or approved.
- Every developer has to check constantly if there were any changes to the original project.
- The branches that were approved or rejected must be eliminated
It is recommended to create a new organization that is the owner of the main repository.Starting with this repository all the collaborators and members will do a fork to their accounts
- Click on your profile photo
- Click on settings
- Click on organitation (Left menu)
- Click on new organitation
- Choose the plan and fill up data
For creating a fork you must sign in on Github and then go to the landing page's project of whatever fork you want to do.
Display remotes repositories
git remote -v
Add a remote repository
git remote add {name} {URL}
Delete a remote link
git remote remove {Name}
It is neccesary to understand that the tags only have to be created on the master branch as a good practice.
To understand how to name or set up your new versions we recommend you an article on out blog: https://ed.team/blog/como-se-deciden-las-versiones-del-software