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

With feature branches, what is ever committed directly to master

From
Bradley Wagner <bradley.wagner@hannonhill.com>
Date
Aug 10, 2010, 19:02 UTC
Message-ID
<AANLkTin0VgH8CvnUn_tCJPTkhh7Ce-tYWo52qouoVvRN@mail.gmail.com>

I realize there are a lot of different Git workflows but I'm wondering how others in this community do it.

We're using our "master" branch from our central repo (Beanstalk) as a dev branch and we have stable branches for various release versions of our software.

We've not made as heavy use of feature branches yet as we should have. Once we do start using them more regularly, what kind of stuff is ever committed directly to "master" or is master typically the place where things are merged into from other stable/features branches?

Is "master" really even unstable at that point?
Thanks in advance! I realize this question is pretty open-ended.
Next: Michael Witten
Message 1 of 9 in “With feature branches, what is ever committed directly to master”
  1. Bradley WagnerAug 10, 2010
  2. Michael WittenAug 10, 2010
  3. David RiptonAug 11, 2010
  4. Jon SeymourAug 11, 2010
  5. Steven E. HarrisAug 13, 2010
  6. Jon SeymourAug 13, 2010
  7. Magnus BäckAug 11, 2010
  8. Jon SeymourAug 11, 2010
  9. Tim VisherAug 11, 2010

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.