git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git new features: following and priority branches with new git flow

From
MMMilos Markovic <k4hvd1@gmail.com>
Date
Dec 15, 2025, 10:15 UTC
Message-ID
<CAKRouPtDrCgUk1bQeF+ao04rtK_jg8KxD6Oju8vw8H-ZYt-7Ow@mail.gmail.com>
Dear all,

After decades of using git (as dev, as manager and as a cto), and considering different git flows I noticed some gaps.

Briefly, different git flows perceive branches equally and shape history from developers perspective. I realized that if the perspective is written from a devops perspective ( focusing on higher priority branches, like prod first , than qa, and with least focus on dev) the source history could be organized differently ( from my perspective a bit better). We used the following approach for a couple of years.

Therefore I invite you to check the following workflow here https://github.com/k4hvd1/rebaser-flow .

It would be my pleasure to discuss new features in git and how this approach could be used. Finally if it makes sense for you I will show you other materials and we could think about implementing it in git .

Regards Milos

Next: Kristoffer Haugsbakk
Message 1 of 3 in “git new features: following and priority branches with new git flow”
  1. Milos MarkovicDec 15, 2025
  2. Kristoffer HaugsbakkDec 15, 2025
  3. Milos MarkovicDec 15, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.