Skip to content

Organization repository count includes private repositories #27926

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jrjake opened this issue Nov 6, 2023 · 6 comments
Closed

Organization repository count includes private repositories #27926

jrjake opened this issue Nov 6, 2023 · 6 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug

Comments

@jrjake
Copy link

jrjake commented Nov 6, 2023

Description

If I mark a repository as private in an organization, that repository is still shown in the count for users who can't access it. See example below.

Gitea Version

1.20.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image

It states there is 1 repository (the private one) but has 0 in the list.

Git Version

2.39.2

Operating System

Debian 12

How are you running Gitea?

Docker

Database

PostgreSQL

@jrjake jrjake added the type/bug label Nov 6, 2023
@lng2020
Copy link
Member

lng2020 commented Nov 6, 2023

Could u provide more information about what's the type of the org, public or Private? And what's the relationship between the user and the org?

@jrjake
Copy link
Author

jrjake commented Nov 6, 2023

It is public organization with private repository. The screenshot is taken when not signed in.

@JakobDev
Copy link
Contributor

JakobDev commented Nov 6, 2023

This is already fixed with #25928

@lng2020 lng2020 added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Nov 7, 2023
@jrjake
Copy link
Author

jrjake commented Nov 7, 2023

I see in that PR mentions of backport, should it be fixed in 1.20.5 (current version I am running)? Or did backport not happen?

@lng2020
Copy link
Member

lng2020 commented Nov 7, 2023

It seems to haven't been backported. Looks like there are many conflicts.

@jrjake
Copy link
Author

jrjake commented Nov 7, 2023

Okay, makes sense. I will close this issue and re-open if I encounter it after release and upgrade to 1.21. Thank you all!

@jrjake jrjake closed this as completed Nov 7, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug
Projects
None yet
Development

No branches or pull requests

3 participants