working with teams/ organisation. understanding problem #1907

New Issue

GiteaMirror · 2025-11-02T04:17:30-06:00

GiteaMirror commented

2025-11-02 04:17:30 -06:00

Originally created by @flobee on GitHub (Jun 9, 2018).

Gitea version (or commit ref): 1.4.2
Git version: 2.11.0
Operating system: debian 9 (stretch)
Database (use [x]):
- [ X] SQLite
Can you reproduce the bug at https://try.gitea.io:
- [ X] Yes
  https://try.gitea.io/company

Description

i worked it out now to be a very little issus about the wording: "Transfer Ownership" when writing this request. But i also request for assistant: what do i need then or a how to...:
Maybe there is any doc to understand:

i create an organisation which has:

owner (1,2..
teams (eg for repo write access)
how to deny view access for all others? ....

the repos of the company should be private / not listed but member should have access.

actions i'v done:

    3. flobee transferred repository flobee/company-repo-private to company/company-repo-private
    2. flobee pushed to master at flobee/company-repo-private
    1. flobee created repository flobee/company-repo-private 
    This ---------------------------^^^^ what i'v done, not what it shows now (**flobee**/company-repo-private vs "**company**/company-repo-private"

see screenshot at the bottom.

when a member of the "company" in the team loggs in eg: "test2test2" user
test2test2 can not see any repos (https://try.gitea.io/company)
Just if test2test2 gets owner ship.
In one way this is correct. if a person is the owner and want to keep stuff private. as "company" or group holder?

How to set levels like: team a only see repos they are assigned to and team b some other stuff? Its not about deny access, its about to reduce the overview of repos :)
sounds like i need gitolite as middleware? does that work?

Repo: "Transfer Ownership" is in this case the kind of "bug". I'm still an owner of the repo but its not in my user account anymore. Thats what confuses me to end up in this report.
...

Originally created by @flobee on GitHub (Jun 9, 2018). - Gitea version (or commit ref): 1.4.2 - Git version: 2.11.0 - Operating system: debian 9 (stretch) - Database (use `[x]`): - [ X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ X] Yes https://try.gitea.io/company ## Description i worked it out now to be a very little issus about the wording: "Transfer Ownership" when writing this request. But i also request for assistant: what do i need then or a how to...: Maybe there is any doc to understand: i create an organisation which has: - owner (1,2.. - teams (eg for repo write access) - how to deny view access for all others? .... the repos of the company should be private / not listed but member should have access. actions i'v done: ``` 3. flobee transferred repository flobee/company-repo-private to company/company-repo-private 2. flobee pushed to master at flobee/company-repo-private 1. flobee created repository flobee/company-repo-private This ---------------------------^^^^ what i'v done, not what it shows now (**flobee**/company-repo-private vs "**company**/company-repo-private" see screenshot at the bottom. ``` when a member of the "company" in the team loggs in eg: "test2test2" user test2test2 can not see any repos (https://try.gitea.io/company) Just if test2test2 gets owner ship. In one way this is correct. if a person is the owner and want to keep stuff private. as "company" or group holder? How to set levels like: team a only see repos they are assigned to and team b some other stuff? Its not about deny access, its about to reduce the overview of repos :) sounds like i need gitolite as middleware? does that work? Repo: "**Transfer Ownership**" is in this case the kind of "bug". I'm still an owner of the repo but its not in my user account anymore. Thats what confuses me to end up in this report. ... ![2018-06-09_15-29-28](https://user-images.githubusercontent.com/1349520/41192168-52adf956-6bfa-11e8-9504-6d2f28fa6ec3.png)

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:17:30 -06:00

GiteaMirror closed this issue

2025-11-02 04:17:31 -06:00

GiteaMirror commented

2025-11-02 04:17:31 -06:00

@stale[bot] commented on GitHub (Jan 23, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 23, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:17:31 -06:00

@techknowlogick commented on GitHub (Jan 23, 2019):

Closing issue. Please open a post in the forum for this issue.

@techknowlogick commented on GitHub (Jan 23, 2019): Closing issue. Please open a post in the [forum](https://discourse.gitea.io/) for this issue.

GiteaMirror commented

2025-11-02 04:17:32 -06:00

@flobee commented on GitHub (Mar 15, 2019):

Seems to be implemented in version >1.7.4 👍
Found in release7780ea8 at https://try.gitea.io

@flobee commented on GitHub (Mar 15, 2019): Seems to be implemented in version >1.7.4 :+1: Found in release7780ea8 at https://try.gitea.io

GiteaMirror referenced this issue

2025-11-02 12:02:38 -06:00