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

Generic package owner as {user}/{repo} #14304

New Issue
Closed
opened 2025-11-02 11:09:20 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 11:09:20 -06:00
Owner
Copy Link

Originally created by @xiaozhuai on GitHub (Mar 26, 2025).

Feature Description

I have a repo located under an organization.
I want to publish a Generic package to this repository,
but I don't want members in this organization who do not have this repository permission to see this package.

I tried setting owner to {user}/{repo}, but when PUT with curl, it returned a 404.
I also tried to associate the package with the repo, but this way, all organization members can see and download the package.

What should I do to limit the package to be accessed only by member with the repo permissions?

Screenshots

No response

Originally created by @xiaozhuai on GitHub (Mar 26, 2025). ### Feature Description I have a repo located under an organization. I want to publish a Generic package to this repository, but I don't want members in this organization who do not have this repository permission to see this package. I tried setting owner to {user}/{repo}, but when PUT with curl, it returned a 404. I also tried to associate the package with the repo, but this way, all organization members can see and download the package. What should I do to limit the package to be accessed only by member with the repo permissions? ### Screenshots _No response_
GiteaMirror added the topic/packagestype/proposalissue/duplicate labels 2025-11-02 11:09:20 -06:00
GiteaMirror commented 2025-11-02 11:09:21 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Apr 3, 2025):

That's currently not possible because package permissions are taken from the owner not a possible linked repository. There is already an issue for more fine granular package permissions.

@KN4CK3R commented on GitHub (Apr 3, 2025): That's currently not possible because package permissions are taken from the owner not a possible linked repository. There is already an issue for more fine granular package permissions.
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/duplicate topic/packages type/proposal
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#14304
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?