Organization team access control dont work

[yp05327]

Description

1. You need to have two account. One is admin user1, the other one is normal user2.
2. Use the admin account to create an organization, and create a new repo.
3. Add a new team, set Repository access to All repositories and all unit to No Access except Issue or any other, this is not important.
4. Add user2 to this team
5. Use user2 to access the repo, and all unit can be accessed.

If you check the settings of the repo, you will see this team only has Read permission of Issues.
But user2 can access all units.

create new team

add user2 to this team

user2 can access all unit

the settings of the repo shows the new added team only has Read permission of Issues.

Tips:
try.gitea.io can't create organization so i tested this at gitea.com. All screenshots are taken at gitea.com, not my local server.

Gitea Version

1.18.3, 1.19.0+dev-334-g0c048e554

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

run gitea-1.18.3-windows-4.0-amd64.exe on win10
&
gitea.com

Database

SQLite

[lunny]

Because the repository is a public one, you need to change it to private.

[yp05327]

Change to private is correct.
Thanks.

[yp05327]

@lunny
I think we can add some explanations to avoid making the same mistake again?

eg:

Allow Access to Repository Sections*
The following access control options have no effect on the public repositories in this organization.

[lunny]

Could you help to send a PR for that? Thanks in advance.