What GitFlow was used? What approaches were taken? Was it GitLab self-hosted or something else?

GitFlow is a popular branching model in Git that involves using main branches master (or main) and develop, as well as auxiliary branches for features, releases, and fixes.

Approaches typically used in GitFlow include:

• The develop branch as the main development branch.
• feature/* branches for new features, which are later merged into develop.
• release/* branches for preparing releases.
• hotfix/* branches for urgent fixes in master.

Regarding infrastructure, GitLab self-hosted is often used for managing repositories, CI/CD, and access control. It allows integrating GitFlow into development processes through merge requests, pipelines, and branch protection rules.

If you have used GitLab self-hosted, it is likely that protected branches were configured for master and develop, along with automation of checks and builds during branch merges.

Overall, the approach depends on the specific project, but the described methods are standard for GitFlow and GitLab self-hosted.