Adding permissions control for source code attachments #9886

New Issue

GiteaMirror · 2025-11-02T08:52:17-06:00

GiteaMirror commented

2025-11-02 08:52:17 -06:00

Originally created by @4EarHeart1 on GitHub (Nov 25, 2022).

Feature Description

My requirement

I want to implement closed-source hosting of a repository in gitea.

Description

Right now gitea can control the visibility of code modules and release-modules for teams in the organization, but I would like to open up the access to my release attachments, but unfortunately I find that gitea cannot do that at the moment. The first reason is that the release automatically packages the source code program as a release attachment, and the second reason is that access to tags cannot be controlled separately.

My expectations

1、Add the option of whether to include source code attachments when releasing a version.
2、Add access rights control of tags, or control whether tags show source code.

Screenshots

Originally created by @4EarHeart1 on GitHub (Nov 25, 2022). ### Feature Description ## My requirement I want to implement closed-source hosting of a repository in gitea. ## Description Right now gitea can control the visibility of code modules and release-modules for teams in the organization, but I would like to open up the access to my release attachments, but unfortunately I find that gitea cannot do that at the moment. The first reason is that the release automatically packages the source code program as a release attachment, and the second reason is that access to tags cannot be controlled separately. ## My expectations 1、Add the option of whether to include source code attachments when releasing a version. 2、Add access rights control of tags, or control whether tags show source code. ### Screenshots ![image](https://user-images.githubusercontent.com/64122863/203932858-f965347a-f02c-4c73-84b3-28722aba5d56.png) ![image](https://user-images.githubusercontent.com/64122863/203932880-4f441f13-7d50-4711-aae7-d6a68ffc31c4.png) ![image](https://user-images.githubusercontent.com/64122863/203932908-f711a923-093f-4ae5-bead-81db41409c82.png)

GiteaMirror added the issue/not-a-bug label 2025-11-02 08:52:17 -06:00

GiteaMirror closed this issue

2025-11-02 08:52:17 -06:00

GiteaMirror commented

2025-11-02 08:52:18 -06:00

@lunny commented on GitHub (Nov 25, 2022):

If one can't view Code tab, then he cannot visit that. This has been implemented.

@lunny commented on GitHub (Nov 25, 2022): If one can't view `Code` tab, then he cannot visit that. This has been implemented.

GiteaMirror commented

2025-11-02 08:52:18 -06:00

@4EarHeart1 commented on GitHub (Nov 25, 2022):

I'm sorry, I thought I could only control the display of the module, but I tried it now. Thank you very much.

@4EarHeart1 commented on GitHub (Nov 25, 2022): I'm sorry, I thought I could only control the display of the module, but I tried it now. Thank you very much.

GiteaMirror commented

2025-11-02 08:52:18 -06:00

@4EarHeart1 commented on GitHub (Nov 25, 2022):

#21773 Please follow up, thank you!

@4EarHeart1 commented on GitHub (Nov 25, 2022): #21773 Please follow up, thank you!

GiteaMirror commented

2025-11-02 08:52:18 -06:00

@lunny commented on GitHub (May 31, 2023):

I think this has already been implemented. If code is disabled or unreachable, these archives will not be displayed in releases.

@lunny commented on GitHub (May 31, 2023): I think this has already been implemented. If code is disabled or unreachable, these archives will not be displayed in releases.

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#9886