Skip to content
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

[Bug Report] Unstar private repos #18600

Closed
schorsch13 opened this issue Feb 4, 2022 · 5 comments · Fixed by #19904
Closed

[Bug Report] Unstar private repos #18600

schorsch13 opened this issue Feb 4, 2022 · 5 comments · Fixed by #19904
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Milestone

Comments

@schorsch13
Copy link
Contributor

Introduction

Suppose that Alice stars a repo from Bob. Bob decides to make his repo private. Alice now has 1 starred repo but is unable to view it.

Example

https://try.gitea.io/schorsch2?tab=stars

image

Proposal

Either remove the stars if a repo is being made private or count only public repos when displaying the amount of starred repos at the profile page

Credits

This bug was discovered by the codeberg user baobab. For further information have a look at the issue at codeberg: https://codeberg.org/Codeberg/Community/issues/480

@firephreek
Copy link

What should happen if Bob restores his repo status to Public?

  • Should Alice have to re-favorite Bob's Repo or should it be automatically 're-added'?
  • Should there be a notification?

@schorsch13
Copy link
Contributor Author

Thats the thing. I think therefore it makes sense to not remove the star but decrease the counter on the profile page

@lunny lunny added the type/bug label Feb 9, 2022
@techknowlogick
Copy link
Member

FWIW GitHub removes all stars when made private, source: https://twitter.com/github/status/1493329046708670475

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Apr 16, 2022
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Apr 17, 2022
@stale stale bot removed the issue/stale label Apr 17, 2022
@lunny
Copy link
Member

lunny commented Apr 17, 2022

Looks like we can follow Github's method.

42wim added a commit to 42wim/gitea that referenced this issue Jun 6, 2022
6543 pushed a commit that referenced this issue Jun 5, 2023
@6543 6543 added this to the 1.20.0 milestone Jun 5, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants