Feature Hidden Branches #4988

New Issue

GiteaMirror · 2025-11-02T06:10:10-06:00

GiteaMirror commented

2025-11-02 06:10:10 -06:00

Originally created by @6543 on GitHub (Mar 2, 2020).

Idear: like hidden issue but for a branch (to develop a securety fix or have specific secret files/infos/config versioned but be able po publish the rest ...)

Originally created by @6543 on GitHub (Mar 2, 2020). Idear: like hidden issue but for a branch (to develop a securety fix or have specific secret files/infos/config versioned but be able po publish the rest ...)

GiteaMirror added the type/proposal label 2025-11-02 06:10:10 -06:00

GiteaMirror closed this issue

2025-11-02 06:10:11 -06:00

GiteaMirror commented

2025-11-02 06:10:11 -06:00

@guillep2k commented on GitHub (Mar 3, 2020):

I'm not sure it's possible using git. A git fetch will bring everything to the client. It will be more like a "treat with discretion" branch.

@guillep2k commented on GitHub (Mar 3, 2020): I'm not sure it's possible using git. A `git fetch` will bring everything to the client. It will be more like a "treat with discretion" branch.

GiteaMirror commented

2025-11-02 06:10:11 -06:00

@6543 commented on GitHub (Mar 3, 2020):

if git we can filt reverences of git I think this is posible ... but I dont know/looked-at the internals how git fetch is handled so i only can gues for now

@6543 commented on GitHub (Mar 3, 2020): if git we can filt reverences of git I think this is posible ... but I dont know/looked-at the internals how git fetch is handled so i only can gues for now

GiteaMirror commented

2025-11-02 06:10:12 -06:00

@zeripath commented on GitHub (Mar 5, 2020):

There's other problems with guessing shas, the private objects would need to be kept completely within a separate object db.

@zeripath commented on GitHub (Mar 5, 2020): There's other problems with guessing shas, the private objects would need to be kept completely within a separate object db.

GiteaMirror commented

2025-11-02 06:10:12 -06:00

@zeripath commented on GitHub (Mar 5, 2020):

At which point it starts to look a lot like a private fork...

@zeripath commented on GitHub (Mar 5, 2020): At which point it starts to look a lot like a private fork...

GiteaMirror commented

2025-11-02 06:10:12 -06:00

@lunny commented on GitHub (Mar 6, 2020):

We may could replace git http protocol when you read refs/heads and ssh protocol on gitea serv.

@lunny commented on GitHub (Mar 6, 2020): We may could replace git http protocol when you read `refs/heads` and ssh protocol on `gitea serv`.

GiteaMirror commented

2025-11-02 06:10:12 -06:00

@zeripath commented on GitHub (Mar 6, 2020):

It's not just the ref heads it's all the objects associated with the ref heads. You can't pack any objects from the private refs into packs that non authorized users can download.

Private branches are why gitlab can't support git v2 wire protocol.

The best answer is probably to better support forks - allow porting of PRs between forks, perhaps allow private forks of org projects to permit team members etc.

@zeripath commented on GitHub (Mar 6, 2020): It's not just the ref heads it's all the objects associated with the ref heads. You can't pack any objects from the private refs into packs that non authorized users can download. Private branches are why gitlab can't support git v2 wire protocol. The best answer is probably to better support forks - allow porting of PRs between forks, perhaps allow private forks of org projects to permit team members etc.

GiteaMirror commented

2025-11-02 06:10:13 -06:00

@6543 commented on GitHub (Mar 6, 2020):

I think this was a nice idear but a private fork can act similar ...

@6543 commented on GitHub (Mar 6, 2020): I think this was a nice idear but a private fork can act similar ...

GiteaMirror commented

2025-11-02 06:10:13 -06:00

@6543 commented on GitHub (Mar 6, 2020):

It looks like implementing would result in more resource usage and dev time ... so close it?

@6543 commented on GitHub (Mar 6, 2020): It looks like implementing would result in more resource usage and dev time ... so close it?

GiteaMirror commented

2025-11-02 06:10:13 -06:00

@a1012112796 commented on GitHub (Mar 23, 2020):

It's really attractive , but may be it was hard because of git's permission and hock system not have suport , may be we should directly do some change on git, to make it have more permission choices.
by the way, dose we have hidden issue function now, thanks.

@a1012112796 commented on GitHub (Mar 23, 2020): It's really attractive , but may be it was hard because of git's permission and hock system not have suport , may be we should directly do some change on git, to make it have more permission choices. by the way, dose we have hidden issue function now, thanks.

GiteaMirror commented

2025-11-02 06:10:14 -06:00

@6543 commented on GitHub (Mar 27, 2020):

@a1012112796 -> #3217 (no, we dont)

@6543 commented on GitHub (Mar 27, 2020): @a1012112796 -> #3217 (no, we dont)

GiteaMirror referenced this issue

2025-11-02 14:12:23 -06:00

[PR #4990] [MERGED] Fix #rrggbbaa color to rgba for better browser compatibility #17580

Sign in to join this conversation.