Re: Git private branch Feature Suggestion
- From
- Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
- Date
- Sep 11, 2025, 08:15 UTC
- Message-ID
- <fccd1ea3-c57d-4c41-a31b-f0563848416a@app.fastmail.com>
- In-Reply-To
- <CAGyVUB5QLV+HQMWT+0kDu1_H0uXHK7kTy35WqhXQaETZ5if5EQ@mail.gmail.com>
On Thu, Sep 11, 2025, at 01:28, ynckz wrote:
Show 14 quoted lines
> Hi Git developers, > > 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.
I use a sibling repository `.git-mine` with files that don’t overlap with those from `.git`. This way I can have two “working trees” checked out.
-- Kristoffer Haugsbakk