Public issue trackers and/or wikis for private repositories

[FM-96]

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! We accept bounties via Bountysource.

[bkcsoft]

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]

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

[strk]

The feature just landed in Gogs, see:
gogs/gogs#649 (comment)

Commit gogs/gogs@8196430

[perfaram]

What's the current state of this issue ?

[lunny]

No people are working on this.

[perfaram]

Thanks for the quick reply, @lunny !

[lunny]

I'm working on this, see #5833

[stale]

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.

[RDmitchell]

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]

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

[SugarD-x]

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]

Also very relevant to us.

[timgrote]

I'd love to be able to leverage this.

[RDmitchell]

Yes this would be incredibly useful ...

[FrostKiwi]

I had kick-started an issue of the same concern: #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: #22074 (comment) and @a1012112796 suggested here: #22074 (comment) 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 #22074 (comment) , 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]

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.