Admin-Users cannot clone repos of other organizations #930

New Issue

GiteaMirror · 2025-11-02T03:42:03-06:00

GiteaMirror commented

2025-11-02 03:42:03 -06:00

Originally created by @pree on GitHub (Jul 31, 2017).

Gitea version (or commit ref): a804f0e052300032e2aa84518f7b4c95736a5718
Git version: 2.13.3
Operating system: linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No (No Admin access)
- Not relevant
Log gist:

Description

As an Admin User you cannot clone repos via HTTP/HTTPS which you are not a member of, even though you can see the Repository on the UI.

Originally created by @pree on GitHub (Jul 31, 2017). - Gitea version (or commit ref): `a804f0e052300032e2aa84518f7b4c95736a5718` - Git version: `2.13.3` - Operating system: `linux` - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No (No Admin access) - [ ] Not relevant - Log gist: ## Description As an Admin User you cannot clone repos via HTTP/HTTPS which you are not a member of, even though you can see the Repository on the UI.

GiteaMirror added the type/proposal type/enhancement labels 2025-11-02 03:42:03 -06:00

GiteaMirror commented

2025-11-02 03:42:04 -06:00

@lunny commented on GitHub (Aug 1, 2017):

Should the admin do that?

@lunny commented on GitHub (Aug 1, 2017): Should the admin do that?

GiteaMirror commented

2025-11-02 03:42:04 -06:00

@pree commented on GitHub (Aug 1, 2017):

The admin can see the repositories on the website and so download the zips, so I don't see why this should be an problem.

For Continuous Integration (eg. drone) its useful when a admin account is possible to clone, since the admin account doesn't have to be added to the repositories then.

@pree commented on GitHub (Aug 1, 2017): The admin can see the repositories on the website and so download the zips, so I don't see why this should be an problem. For Continuous Integration (eg. drone) its useful when a admin account is possible to clone, since the admin account doesn't have to be added to the repositories then.

GiteaMirror commented

2025-11-02 03:42:04 -06:00

@lafriks commented on GitHub (Aug 1, 2017):

@appleboy can you comment on drone gitea integration?

@lafriks commented on GitHub (Aug 1, 2017): @appleboy can you comment on drone gitea integration?

GiteaMirror commented

2025-11-02 03:42:04 -06:00

@bkcsoft commented on GitHub (Aug 24, 2017):

@lunny Cloning from should be fine, but pushing to is not IMO. There are obviously corner-cases to that (people having copyrighted material in a repo for example...)

@bkcsoft commented on GitHub (Aug 24, 2017): @lunny Cloning from should be fine, but pushing to is not IMO. There are obviously corner-cases to that (people having copyrighted material in a repo for example...)

GiteaMirror commented

2025-11-02 03:42:05 -06:00

@lunny commented on GitHub (Aug 24, 2017):

~~I remember I have fixed that and override by another PR.~~

@lunny commented on GitHub (Aug 24, 2017): ~I remember I have fixed that and override by another PR.~

GiteaMirror commented

2025-11-02 03:42:05 -06:00

@vtemian commented on GitHub (Feb 23, 2018):

Hi!

At Presslabs, we have hundreds of repositories and we need to offer support for all of them. That means that the support team needs access to those repositories all the time, not only in read-only.

I suggest to let admins clone the repository and an option in app.ini can decide whether to let writes or not.

Does this scenario make sense?

@vtemian commented on GitHub (Feb 23, 2018): Hi! At Presslabs, we have hundreds of repositories and we need to offer support for all of them. That means that the support team needs access to those repositories all the time, not only in read-only. I suggest to let admins clone the repository and an option in `app.ini` can decide whether to let writes or not. Does this scenario make sense?

GiteaMirror commented

2025-11-02 03:42:05 -06:00

@lafriks commented on GitHub (Feb 23, 2018):

if that is made as an option to keep current behavior than it is ok with me

@lafriks commented on GitHub (Feb 23, 2018): if that is made as an option to keep current behavior than it is ok with me

GiteaMirror commented

2025-11-02 03:42:05 -06:00

@lunny commented on GitHub (Feb 24, 2018):

So we need a PR to do that.

@lunny commented on GitHub (Feb 24, 2018): So we need a PR to do that.

GiteaMirror commented

2025-11-02 03:42:06 -06:00