Public Wiki and Issues in private Repo #1124

New Issue

GiteaMirror · 2025-11-02T03:49:21-06:00

GiteaMirror commented

2025-11-02 03:49:21 -06:00

Originally created by @ModdyLP on GitHub (Oct 6, 2017).

Gitea version (or commit ref): 1.2.0-rc3
Git version: latest
Operating system: ubuntu 16.04
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL): https://try.gitea.io/ModdyLP/test/issues
- No
- Not relevant
Log gist:

Description

I want to use the feature of Gogs, which allows the user to access the issues and wiki pages, even it is a private repository. That would be a really nice feature, if you want to provide help for your software, but dont want to grant users access to the sourcecode.

Kind Regards
ModdyLP

Originally created by @ModdyLP on GitHub (Oct 6, 2017). - Gitea version (or commit ref): 1.2.0-rc3 - Git version: latest - Operating system: ubuntu 16.04 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL): https://try.gitea.io/ModdyLP/test/issues - [ ] No - [ ] Not relevant - Log gist: ## Description I want to use the feature of Gogs, which allows the user to access the issues and wiki pages, even it is a private repository. That would be a really nice feature, if you want to provide help for your software, but dont want to grant users access to the sourcecode. Kind Regards ModdyLP

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 03:49:21 -06:00

GiteaMirror closed this issue

2025-11-02 03:49:21 -06:00

GiteaMirror commented

2025-11-02 03:49:22 -06:00

@bkcsoft commented on GitHub (Oct 16, 2017):

We have Units that could be used for this. But there's no way to do this yet outside of a Organization.

@bkcsoft commented on GitHub (Oct 16, 2017): We have Units that could be used for this. But there's no way to do this yet outside of a Organization.

GiteaMirror commented

2025-11-02 03:49:22 -06:00

@ModdyLP commented on GitHub (Oct 16, 2017):

I am looking into Go and try to implement it, i am not sure if I can finish it, but i will learn and try. 😆 Anyone who knows, how to implement it, here is the Gogs Commit Referenz where it is implemented into Gogs 8196430f47

@ModdyLP commented on GitHub (Oct 16, 2017): I am looking into Go and try to implement it, i am not sure if I can finish it, but i will learn and try. :laughing: Anyone who knows, how to implement it, here is the Gogs Commit Referenz where it is implemented into Gogs https://github.com/gogits/gogs/commit/8196430f47842fba4f227b105cd96d4b981d077d

GiteaMirror commented

2025-11-02 03:49:22 -06:00

@lunny commented on GitHub (Oct 16, 2017):

It's not satisfied with this requirement. We need merge access and team_unit tables or something user_unit tables to resolve this. And something for anonymous.

@lunny commented on GitHub (Oct 16, 2017): It's not satisfied with this requirement. We need merge `access` and `team_unit` tables or something `user_unit` tables to resolve this. And something for anonymous.

GiteaMirror commented

2025-11-02 03:49:22 -06:00

@ModdyLP commented on GitHub (Oct 16, 2017):

I cant follow you, maybe because i don't know the structure of gitea as complete system, only parts of it. Can you explain your comment a bit more in detail ?

@ModdyLP commented on GitHub (Oct 16, 2017): I cant follow you, maybe because i don't know the structure of gitea as complete system, only parts of it. Can you explain your comment a bit more in detail ?

GiteaMirror commented

2025-11-02 03:49:22 -06:00

@bkcsoft commented on GitHub (Oct 18, 2017):

@ModdyLP In short, the access-table keeps track of who has access to a repo. While team_unit-table keeps track of which teams has access to which parts of the repo.

@bkcsoft commented on GitHub (Oct 18, 2017): @ModdyLP In short, the `access`-table keeps track of who has access to a repo. While `team_unit`-table keeps track of which teams has access to which parts of the repo.

GiteaMirror commented

2025-11-02 03:49:23 -06:00

@lunny commented on GitHub (Oct 19, 2017):

@bkcsoft maybe we should have a propose issue to describe a new permission design.

@lunny commented on GitHub (Oct 19, 2017): @bkcsoft maybe we should have a propose issue to describe a new permission design.

GiteaMirror commented

2025-11-02 03:49:23 -06:00

@ModdyLP commented on GitHub (Mar 5, 2018):

Are there any updates ? I have looked into, but gitea is for me for now to complex.

@ModdyLP commented on GitHub (Mar 5, 2018): Are there any updates ? I have looked into, but gitea is for me for now to complex.

GiteaMirror commented

2025-11-02 03:49:23 -06:00

@frontbear commented on GitHub (Sep 28, 2018):

This feature is very useful 👍

@frontbear commented on GitHub (Sep 28, 2018): This feature is very useful 👍

GiteaMirror commented

2025-11-02 03:49:23 -06:00

@stale[bot] commented on GitHub (Jan 8, 2019):

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.

@stale[bot] commented on GitHub (Jan 8, 2019): 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.

GiteaMirror commented

2025-11-02 03:49:23 -06:00

@talentant commented on GitHub (Jun 26, 2019):

Any progress on this feature ? It seems to be very useful ! 👍

@talentant commented on GitHub (Jun 26, 2019): Any progress on this feature ? It seems to be very useful ! 👍

GiteaMirror commented

2025-11-02 03:49:24 -06:00

@BaxAndrei commented on GitHub (Jan 7, 2021):

Also might help access to Project Board? I`d like this

@BaxAndrei commented on GitHub (Jan 7, 2021): Also might help access to Project Board? I`d like this

GiteaMirror commented

2025-11-02 03:49:24 -06:00