Git Branching Strategies:
What are the branches you've used, and what are they for? When we establish a repository, it creates a default branch called master.
If you're new to Git, check out these resources to learn the fundamentals:
We will keep a minimum of three environments in any project. We will maintain three branches in a project before deploying code to production.
- Development environment
- QA -test
- Production -end users/customers
1. Development Environment:
We will deploy code to the development environment for developers to utilise after work is completed, and it will integrate with the master/stage branch.
2. Quality Evaluation:
Once the development team is finished, it will integrate from the master branch to the QA branch. Testers will not be able to integrate with the production environment until QA is completed.
3. Production
If the quality checks from the test environment/testers are completed, the code will only deploy to production from the master branch.-This is being worked on by customers/end users.
Check out the top reader picks as well
Refer to the diagram:
Branching strategy |
Other commands
#git rebase
#git rebase
After integrating with master, we have a clear picture of all commit messages. If we combine all commits, we take it as one commit object and integrate with master, however we don't have each commit id details after integration.
README.md file
- Which includes the project title and description
- How it can help contributors and those just starting out.
- How users can begin using your projects.
- Prerequisites for using it.
Thank you for continuing to read; for more information, keep checking back here.