github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Public issue trackers and/or wikis for private repositories #218

New Issue
Closed
opened 2025-11-02 03:14:14 -06:00 by GiteaMirror · 30 comments
GiteaMirror commented 2025-11-02 03:14:14 -06:00
Owner
Copy Link

Originally created by @FM-96 on GitHub (Jan 10, 2017).

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.

Originally created by @FM-96 on GitHub (Jan 10, 2017). 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. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40819688-public-issue-trackers-and-or-wikis-for-private-repositories?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the issue/confirmedtype/feature labels 2025-11-02 03:14:15 -06:00
GiteaMirror commented 2025-11-02 03:14:15 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Feb 12, 2017):

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)

@bkcsoft commented on GitHub (Feb 12, 2017): 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 `pull`able)
GiteaMirror commented 2025-11-02 03:14:16 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 12, 2017):

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

@lunny commented on GitHub (Feb 12, 2017): @bkcsoft, you are right. I will send a PR to put units options on creating Team page, then this issue could be resolved.
GiteaMirror commented 2025-11-02 03:14:16 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Mar 25, 2017):

The feature just landed in Gogs, see:
https://github.com/gogits/gogs/issues/649#issuecomment-289144558

Commit 8196430f47

@strk commented on GitHub (Mar 25, 2017): The feature just landed in Gogs, see: https://github.com/gogits/gogs/issues/649#issuecomment-289144558 Commit https://github.com/gogits/gogs/commit/8196430f47842fba4f227b105cd96d4b981d077d
GiteaMirror commented 2025-11-02 03:14:16 -06:00
Author
Owner
Copy Link

@perfaram commented on GitHub (May 19, 2018):

What's the current state of this issue ?

@perfaram commented on GitHub (May 19, 2018): What's the current state of this issue ?
GiteaMirror commented 2025-11-02 03:14:16 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 19, 2018):

No people are working on this.

@lunny commented on GitHub (May 19, 2018): No people are working on this.
GiteaMirror commented 2025-11-02 03:14:16 -06:00
Author
Owner
Copy Link

@perfaram commented on GitHub (May 25, 2018):

Thanks for the quick reply, @lunny !

@perfaram commented on GitHub (May 25, 2018): Thanks for the quick reply, @lunny !
GiteaMirror commented 2025-11-02 03:14:17 -06:00
Author
Owner
Copy Link

@ceriath commented on GitHub (Jun 4, 2018):

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

@ceriath commented on GitHub (Jun 4, 2018): Would be great if someone could take a look into it!
GiteaMirror commented 2025-11-02 03:14:17 -06:00
Author
Owner
Copy Link

@Bejasc commented on GitHub (Jan 19, 2019):

Any chance someone has decided to dig in to this?

@Bejasc commented on GitHub (Jan 19, 2019): Any chance someone has decided to dig in to this?
GiteaMirror commented 2025-11-02 03:14:17 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 24, 2019):

I'm working on this, see #5833

@lunny commented on GitHub (Jan 24, 2019): I'm working on this, see #5833
GiteaMirror commented 2025-11-02 03:14:17 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 25, 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 (Mar 25, 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:14:18 -06:00
Author
Owner
Copy Link

@tongclement commented on GitHub (Apr 19, 2020):

Want this functionality

@tongclement commented on GitHub (Apr 19, 2020): Want this functionality
GiteaMirror commented 2025-11-02 03:14:18 -06:00
Author
Owner
Copy Link

@mdbergmann commented on GitHub (Aug 4, 2020):

This would definitely be a highly wanted feature for us.

@mdbergmann commented on GitHub (Aug 4, 2020): This would definitely be a highly wanted feature for us.
GiteaMirror commented 2025-11-02 03:14:18 -06:00
Author
Owner
Copy Link

@yafarida commented on GitHub (Aug 31, 2020):

Hey! +1, need this feature. We use wiki and issues to communicate with users, but our sources are private. Now we have to create duplicated repositories like HeroEditor (private) and HeroEditorHub (public).

@yafarida commented on GitHub (Aug 31, 2020): Hey! +1, need this feature. We use wiki and issues to communicate with users, but our sources are private. Now we have to create duplicated repositories like HeroEditor (private) and HeroEditorHub (public).
GiteaMirror commented 2025-11-02 03:14:18 -06:00
Author
Owner
Copy Link

@Jakar510 commented on GitHub (Sep 3, 2020):

+1, but only if it's optional.

@Jakar510 commented on GitHub (Sep 3, 2020): +1, but only if it's optional.
GiteaMirror commented 2025-11-02 03:14:19 -06:00
Author
Owner
Copy Link

@interior-night commented on GitHub (Nov 30, 2020):

Also interested.

@interior-night commented on GitHub (Nov 30, 2020): Also interested.
GiteaMirror commented 2025-11-02 03:14:19 -06:00
Author
Owner
Copy Link

@kdaner commented on GitHub (Jan 24, 2021):

Also interested if optional. I can do this on my bitbucket repos.

@kdaner commented on GitHub (Jan 24, 2021): Also interested if optional. I can do this on my bitbucket repos.
GiteaMirror commented 2025-11-02 03:14:19 -06:00
Author
Owner
Copy Link

@RDmitchell commented on GitHub (Mar 24, 2021):

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.

@RDmitchell commented on GitHub (Mar 24, 2021): 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.
GiteaMirror commented 2025-11-02 03:14:19 -06:00
Author
Owner
Copy Link

@rlogiacco commented on GitHub (May 27, 2021):

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

@rlogiacco commented on GitHub (May 27, 2021): I would like to sponsor the development of this feature as I need it as well....
GiteaMirror commented 2025-11-02 03:14:20 -06:00
Author
Owner
Copy Link

@SugarD-x commented on GitHub (Sep 2, 2021):

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!

@SugarD-x commented on GitHub (Sep 2, 2021): 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!
GiteaMirror commented 2025-11-02 03:14:20 -06:00
Author
Owner
Copy Link

@joaobarcia commented on GitHub (Dec 14, 2021):

Also very relevant to us.

@joaobarcia commented on GitHub (Dec 14, 2021): Also very relevant to us.
GiteaMirror commented 2025-11-02 03:14:20 -06:00
Author
Owner
Copy Link

@timgrote commented on GitHub (Feb 27, 2022):

I'd love to be able to leverage this.

@timgrote commented on GitHub (Feb 27, 2022): I'd love to be able to leverage this.
GiteaMirror commented 2025-11-02 03:14:20 -06:00
Author
Owner
Copy Link

@RDmitchell commented on GitHub (Feb 27, 2022):

Yes this would be incredibly useful ...

@RDmitchell commented on GitHub (Feb 27, 2022): Yes this would be incredibly useful ...
GiteaMirror commented 2025-11-02 03:14:21 -06:00
Author
Owner
Copy Link

@FrostKiwi commented on GitHub (Jul 10, 2023):

I had kick-started an issue of the same concern: https://github.com/go-gitea/gitea/issues/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: https://github.com/go-gitea/gitea/issues/22074#issuecomment-1422188191 and @a1012112796 suggested here: https://github.com/go-gitea/gitea/issues/22074#issuecomment-1545435233 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 https://github.com/go-gitea/gitea/issues/22074#issuecomment-1545403181 , 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.

@FrostKiwi commented on GitHub (Jul 10, 2023): I had kick-started an issue of the same concern: https://github.com/go-gitea/gitea/issues/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: https://github.com/go-gitea/gitea/issues/22074#issuecomment-1422188191 and @a1012112796 suggested here: https://github.com/go-gitea/gitea/issues/22074#issuecomment-1545435233 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 https://github.com/go-gitea/gitea/issues/22074#issuecomment-1545403181 , 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.
GiteaMirror commented 2025-11-02 03:14:21 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Apr 15, 2024):

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.

@wxiaoguang commented on GitHub (Apr 15, 2024): 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.
GiteaMirror commented 2025-11-02 03:14:21 -06:00
Author
Owner
Copy Link

@cstayyab commented on GitHub (Dec 19, 2024):

Any further progress on this?

@cstayyab commented on GitHub (Dec 19, 2024): Any further progress on this?
GiteaMirror commented 2025-11-02 03:14:21 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 19, 2024):

No update means no progress at the moment. Gitea is quite large and there are so many TODOs ........

@wxiaoguang commented on GitHub (Dec 19, 2024): No update means no progress at the moment. Gitea is quite large and there are so many TODOs ........
GiteaMirror commented 2025-11-02 03:14:21 -06:00
Author
Owner
Copy Link

@cstayyab commented on GitHub (Dec 19, 2024):

Can you point me to somewhere to start so I can help with this? may be submit a PR myself

@cstayyab commented on GitHub (Dec 19, 2024): Can you point me to somewhere to start so I can help with this? may be submit a PR myself
GiteaMirror commented 2025-11-02 03:14:22 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 19, 2024):

Maybe you could take a look at Allow everyone to read or write a wiki by a repo unit setting #30495 , it makes Wiki could be accessed publicly.

The EveryoneAccessMode field has been added to "ReopUnit", so I guess other units (like "issues") could also use it.

@wxiaoguang commented on GitHub (Dec 19, 2024): Maybe you could take a look at Allow everyone to read or write a wiki by a repo unit setting #30495 , it makes Wiki could be accessed publicly. The `EveryoneAccessMode` field has been added to "ReopUnit", so I guess other units (like "issues") could also use it.
GiteaMirror commented 2025-11-02 03:14:22 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jan 7, 2025):

We can have this feature in 1.24: Support public code/issue access for private repositories #33127

Create a private repo, and set Default access permission for all signed-in users: to Read

@wxiaoguang commented on GitHub (Jan 7, 2025): We can have this feature in 1.24: Support public code/issue access for private repositories #33127 Create a private repo, and set `Default access permission for all signed-in users:` to `Read`
GiteaMirror commented 2025-11-02 03:14:22 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Mar 28, 2025):

The complete solution: Add anonymous access support for private repositories #34051 , we will have it in 1.24

@wxiaoguang commented on GitHub (Mar 28, 2025): The complete solution: Add anonymous access support for private repositories #34051 , we will have it in 1.24
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed type/feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#218
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?