mikha

<div>
<div class="content wysiwyg-content fr-view">
I am planning to use github for code repository and hook up the main/master branch CD/CI pipeline. <br><br>in a small team with 2-3 developers, i'm not sure if i need stick with a certain workflow for branching . so far, I want to lockdown the master branch ( need to figure out how to do this in github) such that only code can be merged after a pull request is approved then merged, but not sure what to do, if some immediate issue arises , we have to fix those and push them to master, but if there are any other features that have been merged since the last release , which are not yet to be release, they will be released along with the hot fixes. <br><br>
</div>
</div>



I am planning to use github for code repository and hook up the main/master branch CD/CI pipeline.
in a small team with 2-3 developers, i'm not sure if i need stick with a certain workflow for branching . so far, I want to lockdown the master branch ( need to figure out how to do this in github) such that only code can be merged after a pull request is approved then merged, but not sure what to do, if some immediate issue arises , we have to fix those and push them to master, but if there are any other features that have been merged since the last release , which are not yet to be release, they will be released along with the hot fixes.

git branching for CD/CI pipeline?

Git is a version control system for software development. It is a distributed revision control system with an emphasis on speed, data integrity, and support for distributed, non-linear workflows. Git was initially designed and developed for Linux kernel development. As with most other distributed version control systems, every Git working directory is a full-fledged repository with complete history and full version-tracking capabilities, independent of network access or a central server.