From: <rsbecker@nexbridge•com>
To: "'ynckz'" <yanckezcs@gmail•com>, <git@vger•kernel.org>
Subject: RE: Git private branch Feature Suggestion
Date: Wed, 10 Sep 2025 19:54:34 -0400 [thread overview]
Message-ID: <061501dc22ae$45ac35c0$d104a140$@nexbridge.com> (raw)
In-Reply-To: <CAGyVUB5QLV+HQMWT+0kDu1_H0uXHK7kTy35WqhXQaETZ5if5EQ@mail.gmail.com>
On September 10, 2025 7:29 PM, ynckz wrote:
>I have a request for you. Could you please add private branches? This is a really
>useful thing.
>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:
>Say you don't want to release a new feature yet. To do so, create a private branch,
>make the feature there, then merge it into the main branch.
>
>Maybe I'm a dumb ass, and don't need to ask this of you, but GitLab, etc., anyway,
>I'd appreciate it if you could add this feature.
Put your private content into a submodule and set the visibility of that submodule
to private in GitLab. Your *.env files go in there and will not get shared.
Once you have this working, please try to use polite language instead of what is
In your message. Thanks.
next prev parent reply other threads:[~2025-09-10 23:54 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 [this message]
2025-09-11 0:00 ` brian m. carlson
2025-09-11 0:13 ` Henrique Soares
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='061501dc22ae$45ac35c0$d104a140$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=yanckezcs@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox