The latest articles on DEV Community by Murillo Pinheiro de Oliveria (@muriwolf). https://dev.to/muriwolf https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1595474%2F5bccf81b-59b7-458f-86d5-db12ab369a97.jpeg https://dev.to/muriwolf en Murillo Pinheiro de Oliveria Sun, 19 Jan 2025 15:34:30 +0000 https://dev.to/muriwolf/commom-workflows-with-git-2fbj https://dev.to/muriwolf/commom-workflows-with-git-2fbj <h2> Intro </h2> <p>There are some ways to work with other people using Git, below I demonstrate a few.</p> <h2> Centralized Workflow </h2> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqvwhh4ozdde82sax6mzn.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqvwhh4ozdde82sax6mzn.png" alt="Centralized Workflow" width="800" height="299"></a><br> The most basic flow. The developers use a shared repository to keep the code. If dev A updates the repository, then others dev can't without pulling it. Let's say dev B tried to update, an error will appear to him, and he will only be abble to push after he get the new information with the pull command.</p> <h2> Integration-Manager Workflow </h2> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fssamg8xf2lq1qswgxrm0.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fssamg8xf2lq1qswgxrm0.png" alt="Integration-Manager Workflow&lt;br&gt; " width="800" height="310"></a><br> This one works great on plataforms such as Github, where is easy to created and share repositories.</p> <ol> <li>The maintainer pushes to the public repository;</li> <li>The contributor clones to its own repository;</li> <li>The contributor pushes to its public repository;</li> <li>The contributor sends an email or something communicating the alterations;</li> <li>The mantainer adds the contributor's repository as a remote and merge locally;</li> <li>The mantainer pushes to the main repository.</li> </ol> <h2> Dictator and Lieutenants Workflow </h2> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq583r2kmnu40n82admmb.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq583r2kmnu40n82admmb.png" alt="Dictator and Lieutenants Workflow" width="800" height="423"></a><br> This one is less common and it's better for really big projects. It's used, for example, on Linux project.<br> Off-topic info: Lieutenants comes from french: lieu (place) + tenant (holder).</p> <h2> Ending </h2> <p>I leaned this content in the Pro Git Book, which you can find here: <a href="https://git-scm.com/book/en/v2" rel="noopener noreferrer">https://git-scm.com/book/en/v2</a></p> webdev programming beginners git