From Git-Flow to Github-Flow!

Hello everyone, I have been studying Git workflows seriously 😾 for a few days, aiming to have the broadest possible view and to be able to make suggestions to my team.

In our case, we are using GitFlow for our ETL repository (typical feature branch, develop and main branches, with feature PR and release PR) and I am noticing that, being totally honest with our workflow, we make many release branches that are eventually approved "without looking", as a kind of automatism but performed manually.

While browsing Atlassian's documentation (https://lnkd.in/dwPNE22C), I came across the original article from which GitFlow became popular, and its author, Vincent Driessen, comments that it is really worthwhile to move from GitFlow to GitHub Flow, eliminating the develop branch and having the PR that merges the feature into main carry all the weight, involving the team and understanding that it's more important for a PR to be well done than the fact of having a flow with intermediate steps that give a sense of "checking everything is fine". Here the details of the GitHub Flow: https://lnkd.in/dfAkKDCP

This forces us to have quite fast Deployment and Rollback processes, but I think we can do it and we would save a lot of time and focus on what's important: the PR.

Here is the article by Vincent Driessen, highly recommended to read today with the perspective of 2023: https://lnkd.in/dVXWyn7S

However, each team is a world, and other types of workflows may be of interest.

More information about Git workflows here: https://lnkd.in/d-a_Tg-y