search

go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
https://gitea.com
MIT License
45.1k stars 5.49k forks source link

Public issue trackers and/or wikis for private repositories #639

Open FM-96 opened 7 years ago

FM-96 commented 7 years ago

I would really like it if I could set a repository's issue tracker and/or wiki to public, so that other people can create issues and look at/edit the wiki, even though the repository itself remains private. (I've been mainly using Bitbucket before switching to Gitea and I've always found that functionality very useful.)

Actually, what would be even better (though also probably a lot more work) is if there were seperate permissions for the issue tracker and wiki altogether, so that one could give certain people only read access to the wiki, others write access to the wiki, others access to the issue tracker, etc. I believe Gitlab has a system like that in place.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40819688-public-issue-trackers-and-or-wikis-for-private-repositories?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).
bkcsoft commented 7 years ago

If we extend #742 with AccessRoles mapping Teams<=>Units we could get this fairly simple. The only issue I see is that "private" repos would now be searchable (but not pullable)

lunny commented 7 years ago

@bkcsoft, you are right. I will send a PR to put units options on creating Team page, then this issue could be resolved.

strk commented 7 years ago

The feature just landed in Gogs, see: https://github.com/gogits/gogs/issues/649#issuecomment-289144558

Commit https://github.com/gogits/gogs/commit/8196430f47842fba4f227b105cd96d4b981d077d

perfaram commented 6 years ago

What's the current state of this issue ?

lunny commented 6 years ago

No people are working on this.

perfaram commented 6 years ago

Thanks for the quick reply, @lunny !

ceriath commented 6 years ago

Would be great if someone could take a look into it!

Bejasc commented 5 years ago

Any chance someone has decided to dig in to this?

lunny commented 5 years ago

I'm working on this, see #5833

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

tongclement commented 4 years ago

Want this functionality

mdbergmann commented 4 years ago

This would definitely be a highly wanted feature for us.

yafarida commented 4 years ago

Hey! +1, need this feature. We use wiki and issues to communicate with users, but our sources are private. Now we have to create duplicated repositories like HeroEditor (private) and HeroEditorHub (public).

Jakar510 commented 4 years ago

+1, but only if it's optional.

transat commented 3 years ago

Also interested.

kdaner commented 3 years ago

Also interested if optional. I can do this on my bitbucket repos.

RDmitchell commented 3 years ago

I am confronting this exact issue. I have several private repos that have a large user base as well as some institutional/researchers.

I would love it if I could make the issues public, so that people without access to the private repo could see what we are working on, and potentially contribute issues and comments if needed (not sure if this needs to be a bit more controlled ??).

Anyway, I guess for now I will follow the suggestion of having 2 repos, one for the code, and another for the issues.

rlogiacco commented 3 years ago

I would like to sponsor the development of this feature as I need it as well....

SugarD-x commented 3 years ago

Very much still relevant to me in September 2021 too. The lack of ability to have public issues on a private repo still blows my mind. GitHub is pretty good at being ahead of the curve, so I was expecting this to already be available. Hopefully it is soon!

joaobarcia commented 2 years ago

Also very relevant to us.

timgrote commented 2 years ago

I'd love to be able to leverage this.

RDmitchell commented 2 years ago

Yes this would be incredibly useful ...

FrostKiwi commented 1 year ago

I had kick-started an issue of the same concern: https://github.com/go-gitea/gitea/issues/22074 Since this issue predates my issue, I closed mine and summarize the discussion we had there:

For my specific use-case, due to export laws we cannot set our code as public, but the wiki carries much important project related and info and we want everyone to see and interact with the issue tracker, so anyone can submit bugs. It would be excellent if this could be possible in Gitea.

Right now it's not possible and AFAIK not on the feature roadmap either.

@bendem suggested here: https://github.com/go-gitea/gitea/issues/22074#issuecomment-1422188191 and @a1012112796 suggested here: https://github.com/go-gitea/gitea/issues/22074#issuecomment-1545435233 a similar sentiment: The rights system in Gitea should already be able to perform this, if only there was rights unit anyone.

@delvh suggested in https://github.com/go-gitea/gitea/issues/22074#issuecomment-1545403181 , that code changes by @lunny to disable the code tab were possible steps towards this feature, but that wasn't the case, as the feature in question just disabled the code tab entirely.

From there on out no further discussion was had. Since this issue is older, it would be excellent if future steps towards this feature documented here.

wxiaoguang commented 7 months ago

I have proposed the wiki solution: Allow everyone to read or write a wiki by a repo unit setting #30495

It could be easily extended to support issue tracker later.