Feature Hidden Branches

[6543]

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 ...)

[guillep2k]

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.

[6543]

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

[zeripath]

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

[zeripath]

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

[lunny]

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

[zeripath]

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.

[6543]

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

[6543]

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

[a1012112796]

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.

[6543]

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