Gitea: Public Wiki and Issues in private Repo

Created on 6 Oct 2017  路  10Comments  路  Source: go-gitea/gitea

  • 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:
  • 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

kinfeature revieweconfirmed

Most helpful comment

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

All 10 comments

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

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

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.

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 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 maybe we should have a propose issue to describe a new permission design.

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

This feature is very useful 馃憤

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.

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

Was this page helpful?
0 / 5 - 0 ratings