From: Henrique Soares <henriquegogo@gmail.com>
To: ynckz <yanckezcs@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git private branch Feature Suggestion
Date: Wed, 10 Sep 2025 21:13:24 -0300 [thread overview]
Message-ID: <aMIUJJTUegO3Nzcm@localhost> (raw)
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
next prev parent reply other threads:[~2025-09-11 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 23:28 Git private branch Feature Suggestion ynckz
2025-09-10 23:54 ` rsbecker
2025-09-11 0:00 ` brian m. carlson
2025-09-11 0:13 ` Henrique Soares [this message]
2025-09-11 8:15 ` Kristoffer Haugsbakk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aMIUJJTUegO3Nzcm@localhost \
--to=henriquegogo@gmail.com \
--cc=git@vger.kernel.org \
--cc=yanckezcs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.