Codeberg/Community
54
325
Fork
You've already forked Community
12

unfavorite repositories when they go private #480

Closed
opened 2021年07月01日 04:20:36 +02:00 by baobab · 16 comments

An example of this is when you go to my profile it will show that I favorited three repositories, yet only displaying two of them.

Thanks in advance,

Baobab

Upstream: https://github.com/go-gitea/gitea/pull/19904

An example of this is when you go to my profile it will show that I favorited three repositories, yet only displaying two of them. Thanks in advance, Baobab --- Upstream: https://github.com/go-gitea/gitea/pull/19904

Hmm not that i am aware of.

I think the best way we can do is to fix the counter and let the star stay

Hmm not that i am aware of. I think the best way we can do is to fix the counter and let the star stay
Author
Copy link

Ok, thank you!

Ok, thank you!

Since the problem still occurs (tested it myself), I have forwarded it to upstream: https://github.com/go-gitea/gitea/issues/18600

Since the problem still occurs (tested it myself), I have forwarded it to upstream: https://github.com/go-gitea/gitea/issues/18600

can somebody test if this is fixed with v1.17.0 ?

can somebody test if this is fixed with v1.17.0 ?

Hang on Ill test it real quick

Hang on Ill test it real quick

Nope it is still a thing in Gitea v1.17.0image

Nope it is still a thing in Gitea v1.17.0![image](/attachments/bf8787ed-e669-418a-9945-3c562c798058)

@schorsch

It seems that stars will now be removed when a repo goes private, but I guess fixing leftovers would need a cleanup (gitea doctor)

@schorsch It seems that stars will now be removed when a repo goes private, but I guess fixing leftovers would need a cleanup (gitea doctor)

@ashimokawa are you sure? I just double checked with a newly created repository and it still doesnt work proberly

@ashimokawa are you sure? I just double checked with a newly created repository and it still doesnt work proberly

It seems that stars will now be removed when a repo goes private

Not yet, https://github.com/go-gitea/gitea/pull/19904

> It seems that stars will now be removed when a repo goes private Not yet, https://github.com/go-gitea/gitea/pull/19904

Will be fixed with Gitea v1.18.0

Will be fixed with Gitea v1.18.0

Sorry I missed that, thought it made it into 1.17

Sorry I missed that, thought it made it into 1.17
6543 changed title from (削除) low priority: Is there a way to unfavorite repositories that are set to private? (削除ここまで) to unfavorite repositories when they go private 2022年08月10日 01:15:04 +02:00

Upstream PR isn't merged yet.

[Upstream PR](https://github.com/go-gitea/gitea/pull/19904) isn't merged yet.

Should be fixed now.

Should be fixed now.

Sorry, I closed the issue without making sure that it was indeed resolved as I did in other issues later - the aforementioned PR didn't seem to fully fix the issue.

A subsequent PR can be found here: https://github.com/go-gitea/gitea/pull/26544

Sorry, I closed the issue without making sure that it was indeed resolved as I did in other issues later - the aforementioned PR didn't seem to *fully* fix the issue. A subsequent PR can be found here: https://github.com/go-gitea/gitea/pull/26544

It did fix the issue, https://github.com/go-gitea/gitea/pull/26544 is only related to private repositories you have access to and that they count towards your public total stars.

It did fix the issue, https://github.com/go-gitea/gitea/pull/26544 is only related to private repositories you have access to and that they count towards your public total stars.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#480
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?