Allow the public to create issues on a private server #1945

New Issue

GiteaMirror · 2025-11-02T04:18:43-06:00

GiteaMirror commented

2025-11-02 04:18:43 -06:00

Originally created by @MightyPork on GitHub (Jun 16, 2018).

I apologize if this is a duplicate, didn't find it in the tracker.

I have a self-hosted gitea where I intend to move my projects to. I don't want people creating accounts, organizations and repositories on my server, but I would like them to be able to open issues.

Maybe I missed some config option that would allow this (?) but if no, this would be a valuable improvement. (This could of course be solved by federation, but we aren't there yet)

Gitea version: 1.3.2

Originally created by @MightyPork on GitHub (Jun 16, 2018). I apologize if this is a duplicate, didn't find it in the tracker. I have a self-hosted gitea where I intend to move my projects to. I don't want people creating accounts, organizations and repositories on my server, but I would like them to be able to open issues. Maybe I missed some config option that would allow this (?) but if no, this would be a valuable improvement. (This could of course be solved by federation, but we aren't there yet) - Gitea version: 1.3.2

GiteaMirror added the type/feature type/proposal labels 2025-11-02 04:18:43 -06:00

GiteaMirror closed this issue

2025-11-02 04:18:44 -06:00

GiteaMirror commented

2025-11-02 04:18:45 -06:00

@JamesGKent commented on GitHub (Jun 18, 2018):

I just implemented this option in gogs, I believe the file that would need changing is https://github.com/go-gitea/gitea/blob/master/models/repo_list.go but the code is sufficiently different in gitea that I can't see at a glance what you'd need to change.
for reference my changes to gogs: https://github.com/gogs/gogs/pull/5234/files
and just to explain how it works in gogs, the repo would be shown in search or explore if any part of it is public (code, issues or wiki) but only the public parts of it would show when opened. so for your case the repo should be set to private and the issues set to public.

@JamesGKent commented on GitHub (Jun 18, 2018): I just implemented this option in gogs, I believe the file that would need changing is https://github.com/go-gitea/gitea/blob/master/models/repo_list.go but the code is sufficiently different in gitea that I can't see at a glance what you'd need to change. for reference my changes to gogs: https://github.com/gogs/gogs/pull/5234/files and just to explain how it works in gogs, the repo would be shown in search or explore if any part of it is public (code, issues or wiki) but only the public parts of it would show when opened. so for your case the repo should be set to private and the issues set to public.

GiteaMirror commented

2025-11-02 04:18:45 -06:00

@MightyPork commented on GitHub (Jun 18, 2018):

I'm not sure the proposal was clear enough - this was about creating issues without registration on "public" repos (for a gitea with registrations disabled). Alternatively to allow registration, but without the rights to create repositories - I don't want my small VPS to become another "github" or "gitlab.com".

@MightyPork commented on GitHub (Jun 18, 2018): I'm not sure the proposal was clear enough - this was about creating issues without registration on "public" repos (for a gitea with registrations disabled). Alternatively to allow registration, but without the rights to create repositories - I don't want my small VPS to become another "github" or "gitlab.com".

GiteaMirror commented

2025-11-02 04:18:45 -06:00

@JamesGKent commented on GitHub (Jun 18, 2018):

@MightyPork sorry I misunderstood, I've just realised that what you want would require something like a passwordless guest account or similar. please ignore my comment.

@JamesGKent commented on GitHub (Jun 18, 2018): @MightyPork sorry I misunderstood, I've just realised that what you want would require something like a passwordless guest account or similar. please ignore my comment.

GiteaMirror commented

2025-11-02 04:18:45 -06:00

@MightyPork commented on GitHub (Jun 18, 2018):

Yeah or maybe "login with GitHub" or similar, creating an "external user" account without some permissions. I would consider trying to add this if I knew any Go.

For reference, here is my private server with the public project:
https://git.ondrovo.com/gex/gex-core

And a github mirror (which now has issues on it, as this is where the project started; but I would prefer the issues to live with the upstream):
https://github.com/gexpander/gex-core

@MightyPork commented on GitHub (Jun 18, 2018): Yeah or maybe "login with GitHub" or similar, creating an "external user" account without some permissions. I would consider trying to add this if I knew any Go. For reference, here is my private server with the public project: https://git.ondrovo.com/gex/gex-core And a github mirror (which now has issues on it, as this is where the project started; but I would prefer the issues to live with the upstream): https://github.com/gexpander/gex-core

GiteaMirror commented

2025-11-02 04:18:45 -06:00

@kolaente commented on GitHub (Jun 19, 2018):

As a workaround, you could open your instance for registration but set org and repo limits to 0. That way people could create issues and such, but no repos or orgs.

See https://docs.gitea.io/en-us/config-cheat-sheet/ under "Repository"

@kolaente commented on GitHub (Jun 19, 2018): As a workaround, you could open your instance for registration but set org and repo limits to 0. That way people could create issues and such, but no repos or orgs. See https://docs.gitea.io/en-us/config-cheat-sheet/ under "Repository"

GiteaMirror commented

2025-11-02 04:18:46 -06:00

@leggettc18 commented on GitHub (Feb 3, 2019):

Would that limit also apply to administrator users? Or only to general users? Is there a way to override those settings on a per-user basis? I also want to be able to do this without locking myself out from making more repos.

@leggettc18 commented on GitHub (Feb 3, 2019): Would that limit also apply to administrator users? Or only to general users? Is there a way to override those settings on a per-user basis? I also want to be able to do this without locking myself out from making more repos.

GiteaMirror commented

2025-11-02 04:18:46 -06:00

@kolaente commented on GitHub (Feb 3, 2019):

You can set a per user limit for repos

@kolaente commented on GitHub (Feb 3, 2019): You can set a per user limit for repos

GiteaMirror commented

2025-11-02 04:18:46 -06:00

@MightyPork commented on GitHub (Feb 3, 2019):

I'm using it in that setup and it works correctly, admin isn't limited by the setting. Unless I did something extra to accomplish that, but I don't remember

[repository]
MAX_CREATION_LIMIT = 0

It can be worked around by forking and then re-purposing the fork repo, but i don't think anyone will bother if there's things like GitHub available.

I think we can close this, if this is the official workaround?

@MightyPork commented on GitHub (Feb 3, 2019): I'm using it in that setup and it works correctly, admin isn't limited by the setting. Unless I did something extra to accomplish that, but I don't remember ``` [repository] MAX_CREATION_LIMIT = 0 ``` It can be worked around by forking and then re-purposing the fork repo, but i don't think anyone will bother if there's things like GitHub available. I think we can close this, if this is the official workaround?

GiteaMirror commented

2025-11-02 04:18:47 -06:00

@lunny commented on GitHub (Feb 4, 2019):

I think https://github.com/go-gitea/gitea/pull/5833 will fix this.

@lunny commented on GitHub (Feb 4, 2019): I think https://github.com/go-gitea/gitea/pull/5833 will fix this.

GiteaMirror commented

2025-11-02 04:18:47 -06:00

@mckaygerhard commented on GitHub (Apr 3, 2019):

hi +1 for this wanted feature, seems #5833 are a WIP for this get solved!

@mckaygerhard commented on GitHub (Apr 3, 2019): hi +1 for this wanted feature, seems #5833 are a WIP for this get solved!

GiteaMirror commented

2025-11-02 04:18:47 -06:00

@lunny commented on GitHub (Jul 11, 2019):

It seems this is a duplication of #639

@lunny commented on GitHub (Jul 11, 2019): It seems this is a duplication of #639

GiteaMirror commented

2025-11-02 04:18:47 -06:00

@6543 commented on GitHub (Nov 4, 2019):

Yeah or maybe "login with GitHub" or similar, creating an "external user" account without some permissions. I would consider trying to add this if I knew any Go.

For reference, here is my private server with the public project:
https://git.ondrovo.com/gex/gex-core

And a github mirror (which now has issues on it, as this is where the project started; but I would prefer the issues to live with the upstream):
https://github.com/gexpander/gex-core

@MightyPork

"login with GitHub" is implemented :D
is it a dublicate of #639

so might considder closing this issue ...?

@6543 commented on GitHub (Nov 4, 2019): > Yeah or maybe "login with GitHub" or similar, creating an "external user" account without some permissions. I would consider trying to add this if I knew any Go. > > For reference, here is my private server with the public project: > https://git.ondrovo.com/gex/gex-core > > And a github mirror (which now has issues on it, as this is where the project started; but I would prefer the issues to live with the upstream): > https://github.com/gexpander/gex-core @MightyPork * "login with GitHub" is implemented :D * is it a dublicate of #639 so might considder closing this issue ...?

GiteaMirror commented

2025-11-02 04:18:48 -06:00

@Aviortheking commented on GitHub (Nov 4, 2019):

I thinks it's more like bitbucket have that allow "anonymous" issues

@Aviortheking commented on GitHub (Nov 4, 2019): I thinks it's more like bitbucket have that allow "anonymous" issues

GiteaMirror commented

2025-11-02 04:18:48 -06:00

@xeruf commented on GitHub (Aug 15, 2022):

Yes, guest access, similar as mentioned in https://github.com/go-gitea/gitea/issues/8649#issuecomment-1204513734

@xeruf commented on GitHub (Aug 15, 2022): Yes, guest access, similar as mentioned in https://github.com/go-gitea/gitea/issues/8649#issuecomment-1204513734

GiteaMirror commented

2025-11-02 04:18:49 -06:00

@wxiaoguang commented on GitHub (Apr 8, 2025):

We have it now (in 1.24)

Add anonymous access support for private/unlisted repositories #34051

@wxiaoguang commented on GitHub (Apr 8, 2025): We have it now (in 1.24) Add anonymous access support for private/unlisted repositories #34051 ![image](https://github.com/user-attachments/assets/ef82c18a-fca0-4a0b-818e-c564cfaf3fb2)

GiteaMirror referenced this issue

2025-11-02 12:03:09 -06:00

[PR #1945] [MERGED] [ci skip] add 1.1.2 change log. #16137

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#1945