A Git repository is the storage of code snapshots. It provides a staging area and working directory for Git clients to control.
On the other hand, GitHub provides additional tools around the Git repository. For example, GitHub provides the following:
It provides a web interface to view source code.
It provides a web interface to change files.
It tracks the issues in our work.
It provides collaboration through code comments and discussion.
It provides a web interface to render README files into styled HTML format.
It provides a wiki with additional documentation.
Note: GitHub isn’t the only online repository tool. Others, such as Bitbucket and GitLab, provide similar functionalities.
Different Roles in Git Teams and Team Hierarchy:
The beauty of Git version control is that it enables flexible collaboration between team members or even external developers.
Roles in Git teams:
Imagine a project manager named John is leading a development team. He sets up a Git repository for the development team to use.
On the other side, John sets up a Git repository that connects to the production environment.
John checks for updates of the stable branch from the development team’s Git repository. Then, he pulls the code and pushes it to the production team’s Git repository.
Team hierarchy:
We can set up a team hierarchy that controls people and how they access the repository. It also defines each step of development. For example, see the hierarchy below:
The development team only has access to the development repository.
The project manager manages both the development repository and the production repository.
The QA team that performs quality testing most likely has access to the development repository to pull the latest development branch for testing.
When the code from the development repository is ready, the project manager pushes the code to the production repository, which triggers the compile and build process for production use.
Comentários