Members of an organization cannot open a private repository (owned by the organization) #1139

New Issue

GiteaMirror · 2025-11-02T03:49:50-06:00

GiteaMirror commented

2025-11-02 03:49:50 -06:00

Originally created by @nardhar on GitHub (Oct 11, 2017).

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

Description

Fresh installed Gitea
Created three users: SampleOwner, SampleCollab, SampleExternal
Logged as SampleOwner
Created an organization SampleOrganization and added SampleCollab as a member
Created a private repository and set SampleOrganization as owner
Logged as SampleCollab and can view the repo in the explore tab, but gets a 404 page when tries to open it

Apparently the problem is that it does not add the SampleCollab user as a collaborator since it is a member of the owner organization, I guess it should be allowed to be added nevertheless, I'll investigate more and post more details about this

Thks in advance

Originally created by @nardhar on GitHub (Oct 11, 2017). - Gitea version (or commit ref): 1.2.0 - Git version: 1.8.3.1 - Operating system: Centos 7 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description 1. Fresh installed Gitea 2. Created three users: **SampleOwner**, **SampleCollab**, **SampleExternal** 3. Logged as **SampleOwner** 4. Created an organization **SampleOrganization** and added **SampleCollab** as a member 5. Created a private repository and set **SampleOrganization** as owner 6. Logged as **SampleCollab** and can view the repo in the explore tab, but gets a 404 page when tries to open it Apparently the problem is that it does not add the **SampleCollab** user as a collaborator since it is a member of the owner organization, I guess it should be allowed to be added nevertheless, I'll investigate more and post more details about this Thks in advance

GiteaMirror added the issue/duplicate label 2025-11-02 03:49:50 -06:00

GiteaMirror closed this issue

2025-11-02 03:49:50 -06:00

GiteaMirror commented

2025-11-02 03:49:51 -06:00

@daviian commented on GitHub (Oct 11, 2017):

A member needs to be in a team to have sufficient access rights to repositories.
We have already discussed removing the add member option from UI as it causes confusion and troubles.

Duplicate from #2562, #2593, #1794 and closely related to #2399

@daviian commented on GitHub (Oct 11, 2017): A member needs to be in a team to have sufficient access rights to repositories. We have already discussed removing the `add member` option from UI as it causes confusion and troubles. Duplicate from #2562, #2593, #1794 and closely related to #2399

GiteaMirror commented

2025-11-02 03:49:51 -06:00

@nardhar commented on GitHub (Oct 11, 2017):

having a team as owner works perfectly, but I expected that an organization would work the same, guess I will take the team approach as suggested.

Thanks for the quick response

@nardhar commented on GitHub (Oct 11, 2017): having a team as owner works perfectly, but I expected that an organization would work the same, guess I will take the team approach as suggested. Thanks for the quick response

GiteaMirror referenced this issue

2025-11-02 11:54:34 -06:00

[PR #1149] [MERGED] Fix Git hooks not being executed on Windows when running as a service #15787

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