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

Re: Git private branch Feature Suggestion

From
Henrique Soares <henriquegogo@gmail.com>
Date
Sep 11, 2025, 00:13 UTC
Message-ID
<aMIUJJTUegO3Nzcm@localhost>
In-Reply-To
<CAGyVUB5QLV+HQMWT+0kDu1_H0uXHK7kTy35WqhXQaETZ5if5EQ@mail.gmail.com>
On Thu, Sep 11, 2025 at 02:28:54AM +0300, ynckz wrote:
> I have a request for you. Could you please add private branches? This
> is a really useful thing.

Any branch created locally is private by default. Just don't push it to the remote origin and nobody will have access to it.

> Imagine that you want to publish your project as open source, but you
> need to hide the .env file in a separate repository. It's easier to do
> everything in one repository, but in a different branch. Maybe there
> is another way, and I'm just dumb as fuck, but here's another example:

If you need to share the .env file to few people, but not to everyone, then use a submodule.

-- Henrique
Previous: brian m. carlsonNext: Kristoffer Haugsbakk
Message 4 of 5 in “Git private branch Feature Suggestion”
  1. ynckzSep 10, 2025
  2. rsbecker@nexbridge.comSep 10, 2025
  3. brian m. carlsonSep 11, 2025
  4. Henrique SoaresSep 11, 2025
  5. Kristoffer HaugsbakkSep 11, 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.