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

Git new-feature-branch best practices

From
ZDZganyaiko Dmitry <zdo.str@gmail.com>
Date
Sep 11, 2011, 19:31 UTC
Message-ID
<1315769475.2560.39.camel@mamburu>
Hi all! I have a question about using branches.

For example, I make branch for some experimental feature. After some time I have completed this feature. I'll checkout previous branch and merge this new feature's branch to it.

And there is my question. If I know that this feature was implemented very good and _will not be changed lately_, should I remove this new feature branch (because it will be unused)?

Is there some best practice what to do in my case?

So, should I remove a branch for some new feature after its implementation if I sure that I will not edit this feature's code later?

May be, there is answer for my question already and I missed it?
Next: Alexey Shumkin
Message 1 of 2 in “Git new-feature-branch best practices”
  1. Zganyaiko DmitrySep 11, 2011
  2. Alexey ShumkinSep 12, 2011

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.