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 !

[ceriath]

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

[Bejasc]

Any chance someone has decided to dig in to this?

[lunny]

I'm working on this, see #5833