Now you're here why don't you follow me?!

Bref @oli

petit explication ici: x.com/Baedirl/status/1920272… (le tweet 1 a eu un pb) En (1) je disais **THREAD : Raison du temps de traitement ** 1- Contrôles obligatoires :les banques se doivent de vérifier manuellement chaque transfert pour luttercontre la fraude et le blanchiment.

4h?

Facts! Which brings me to my point Opening a computer is harder than both UI/UX Design, Frontend and Backend

RT @seatedro: claude is the best, this was made in 15 minutes

𝗚𝗶𝘁 𝗕𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗲𝘀 When managing code in software development, choosing the right branching strategy can significantly impact collaboration, integration, and deployment. Here are the main Git branching strategies: 𝟭. 𝗙𝗲𝗮𝘁𝘂𝗿𝗲 𝗯𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴 It involves creating a new branch for each feature or bug fix. Developers work on these branches independently, merging them into the main codebase (usually the main or develop branch) once the work is completed and reviewed. It is best suited for teams that require strict code reviews and where features are developed independently. 𝟮. 𝗚𝗶𝘁𝗳𝗹𝗼𝘄 It is a branching model that defines a strict workflow for managing releases. To organize work, it introduces the concept of develop, release, hotfix, and feature branches. It is best to use it with large projects with scheduled release cycles. 𝟯. 𝗚𝗶𝘁𝗟𝗮𝗯 𝗙𝗹𝗼𝘄 It combines ideas from Feature Branching and Gitflow but simplifies the process. It emphasizes deployment and integrates with issue tracking and continuous deployment. This strategy includes a main branch representing a production-ready code and optional branches per environment (staging, production, etc.). It is best to use it for teams using GitLab integrated tools and if we want to benefit from CD practices. 𝟰. 𝗚𝗶𝘁𝗛𝘂𝗯 𝗙𝗹𝗼𝘄 It is a lightweight, branch-based workflow that is simple and effective for continuous deployment. It focuses on keeping the main branch always in a deployable state. Feature branches are created from the main branch, and we use pull requests to review and merge changes into the main branch. It is best suited for small teams or projects with continuous deployments. 𝟱. 𝗧𝗿𝘂𝗻𝗸-𝗕𝗮𝘀𝗲𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 With this strategy, all developers commit their changes directly to the main branch (the "trunk"). Feature branches are short-lived or avoided altogether. It is best suited for teams that practice continuous integration and delivery and for projects where rapid development is a priority. If you're new to Git workflows, start with a simpler strategy like GitHub Flow and evolve as your team and project grow. For larger teams or more complex projects, consider more structured approaches like Gitflow or GitLab Flow. 👉 Also, regardless of the branching strategy, proper automated testing should be implemented to catch issues earlier and establish team agreements on commit messages, branch naming, and merge procedures. #softwareengineering #programming #coding