🇺🇸🇬🇧 Hello, World! 🇬🇧🇺🇸
English translation is live!

g-flow: A complete and practical #Gitflow implementation:

https://github.com/galvao-eti/g-flow

When the pipeline delivers your change to production

after it sat for 3 days waiting for someone to review your PR

#agile #cicd #notcontinuous #scattergather #gitflow

It’s my first time as #gitflow release manager this week.

So far:
• Overwhelming todo list!
• Struggling with #perfectionism and not being 100% amazing at a new thing the very first time round
• It does feel nice to have a high level overview of the team accomplishments
• Nice break from working on complicated front-end tickets of my own
• It is nice to finally have some understanding of the moving parts at the other end of the #software release cycle

Na sua empresa usa-se Git Flow para estruturar o processo de versionamento de código? Então deixa eu te dar uma má notícia: provavelmente vocês tomaram uma decisão (bem) ruim...

#azuredevops #azurerepos #devops #git #gitflow #github #githubflow

https://t.co/lcdykCpBQF

https://dev.to/maen/contribute-like-a-proa-guide-for-git-branching-model-part-1-4kff - the first steps of embracing #GitFlow: a #Git branching strategy. Nice article https://github.com/maen08.

@jamigibbs feel free to reach out if you have any questions. I'm also working on migrating my personal #WordPress multisite over to a Composer-based setup as well, and I'm using https://buddy.works/ to manage my deployments. I'm using a #Gitflow setup with develop/main/live branches each deploying to Dev/Staging/Production environments.

The "problem" that GitFlow ostensibly solves is that of asynchronous quality gates.

It allows a dev to push code that has not yet been validated, and which may be later validated and promoted piecemeal.

Of course we've known for a long time, and the available evidence keeps growing, that this is a terrible way to ensure quality, or do anything else of value.

#gitflow #trunkbaseddevelopment #qa

Good morning. Please know that if you don’t use a documented #versioning model like #gitflow or others, we are enemies, and we draw pistols at dawn.

Get the Notion template "Visual onboarding with diagrams" https://sudsy-rest-88a.notion.site/Visual-onboarding-with-diagrams-c654d8821c4547c798046359466c14d7 and the "draw.io for Notion" Chrome Extension https://chrome.google.com/webstore/detail/drawio-for-notion/plhaalebpkihaccllnkdaokdoeaokmle #timeline #mindmap #floorplan #gitflow #kanbanboard #flowchart #network #incidentresponseflow #knowledgebank

What does your team dev workflow look like?

Please tick which apply, or comment for more info.

For those who use a monorepo with trunk-based workflow, can you teach me how code review, linting and security testing (e.g. SAST) fit into your workflow?

#MonoRepo #GitFlow #TrunkBasedDevelopment

While checking my bookmarks on #git workflows, I found out that Vincent added a more recent (2020) note to the original post from 2010. He says #gitflow works better when you build software that is explicitly versioned, or you need to support multiple versions. However, for projects that use continuous delivery, it may make more sense to use a lighter, simpler workflow.
https://nvie.com/posts/a-successful-git-branching-model/

What are the most common #git workflow types (I haven't worked with it in a long time)
- feature branch (new features worked in on branches, which are merged back into the main branch afterwards)
- #gitflow (master contains only tagged releases, develop is the central branch; feature and hotfix branches)
- other?

This is in the context of OSS development. #workflow

@tenderlove couldn’t you ask chatGPT how to do it? 🤖

It’s actually a bit shocking that the concept of the „GitHub Flow“ doesn’t consider backporting at all given the amount of open source packages hosted by #GitHub #gitflow

@ale Esse workflow de git One Flow parece atender muito bem casos mais simples. Eu, por exemplo, não sou dev, e os projetos em que participo são bem simples. Acho que o One Flow funcionaria muito bem.
Não sei como seria em casos de projetos mais complexos com muitos devs envolvidos.

#git #gitflow #oneflow #code #dev

Encontrei um material bem legal da Alura, em português, explicando como usar o workflow Git Flow:
https://www.alura.com.br/artigos/git-flow-o-que-e-como-quando-utilizar

#git #gitflow #code #dev

"By the time you need advanced Git — the wheels have already come off car. Let's focus instead on using core Git correctly."

https://blog.trunk.io/minimum-viable-git-for-trunk-based-development-81a5da7a77a7 #git #sourcecontrol #pullrequests #gitflow #trunkbaseddevelopment

I'm going to release a post about preserving of discoveries and failures while working on codebases.

This workflow complements / adjusts #gitflow.

How would you call such workflow? I want to come up with a catchy name. Perhaps then I'll be able to retire into a lavish lifestyle of a "coach".

Someone on Stack Exchange asked about whether #trunkBaseddevelopment and #gitflow are the same. This is my answer (they're not the same at all. One is based, one isn't) https://softwareengineering.stackexchange.com/a/442919/23915

Someone on Stack Exchange asked about whether #trunkBasedDevelopment and #gitflow are the same. This is my answer (they're not the same at all. One is based, one isn't) https://softwareengineering.stackexchange.com/a/442919/23915

The total amount of brain cycles spent by devs on researching/discussing branch management and release approaches is just staggering. I'm a repeat offender/victim. #gitflow #trunkbased