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

Add Repository only View #2371

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

Originally created by @Spenhouet on GitHub (Oct 2, 2018).

Could it be possible to add an option that allows an user only to view a repository he/she is member of.

What I'm proposing is that the user can only open the repository over the unique URL. The user can't enter any other URL.

Instead of this:

image

The user is only able to see the following:

image

There is no header. The user can't enter anything else (also not over URL).

This would be optimal for our use case.
A user with one repository (everything created via API) and the link to this repository with login data is shared with the user. The user can see only the repository view and work on this repository. He/she is unable to see anything else.

I would like to propose this as a feature request. The implementation detail would need to be discussed. I personally think about it in permission rights.

Originally created by @Spenhouet on GitHub (Oct 2, 2018). Could it be possible to add an option that allows an user only to view a repository he/she is member of. What I'm proposing is that the user can only open the repository over the unique URL. The user can't enter any other URL. Instead of this: ![image](https://user-images.githubusercontent.com/7819068/46356720-934a9280-c663-11e8-9c69-4521676d22bb.png) The user is only able to see the following: ![image](https://user-images.githubusercontent.com/7819068/46356744-a3fb0880-c663-11e8-85dc-a901898792cc.png) There is no header. The user can't enter anything else (also not over URL). This would be optimal for our use case. A user with one repository (everything created via API) and the link to this repository with login data is shared with the user. The user can see only the repository view and work on this repository. He/she is unable to see anything else. I would like to propose this as a feature request. The implementation detail would need to be discussed. I personally think about it in permission rights.
GiteaMirror added the type/proposal label 2025-11-02 04:34:01 -06:00
GiteaMirror commented 2025-11-02 04:34:02 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Apr 25, 2023):

https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini#L949-L957

Now you can disable some "units". Feel free to reopen if there is still a problem

@wxiaoguang commented on GitHub (Apr 25, 2023): https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini#L949-L957 Now you can disable some "units". Feel free to reopen if there is still a problem
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 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#2371
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?