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] When repo renamed, ratings split into before and after #55

Open
1 task done
maZahaca opened this issue Dec 30, 2023 · 3 comments
Open
1 task done

[BUG] When repo renamed, ratings split into before and after #55

maZahaca opened this issue Dec 30, 2023 · 3 comments
Labels
🛠 goal: fix 🚦 status: awaiting triage Waiting for maintainers to verify (please do not start work on this yet)

Comments

@maZahaca
Copy link
Member

Has this bug been raised before?

  • I have checked "open" AND "closed" issues and this is not a duplicate

Where did you find this bug?

production

Description

The repo https://github.com/Darginec05/Yopta-Editor was recently renamed to https://github.com/Darginec05/Yoopta-Editor
GitHub handles this by redirecting from an old URL to a new one. Technically this is the the same repository.
After that change, new ratings appear in the repo-rater as new ratings and are not accumulated under the previously named repository.

Steps to Reproduce

  1. Add rating to a repo (repo-a) to repo-rater
  2. Rename repo-a to repo-b (which is technically the same repo)
  3. Add a rating to repo-b to repo-rater.
  4. Find both repo-a and repo-b in the platform with different ratings.

Screenshots

image

Do you want to work on this issue?

No

If "yes" to above, please explain how you would technically implement this

No response

@maZahaca maZahaca added 🚦 status: awaiting triage Waiting for maintainers to verify (please do not start work on this yet) 🛠 goal: fix labels Dec 30, 2023
@eddiejaoude
Copy link
Member

Thank you for raising, renaming of repos/usernames is always tricking to handle 🤔

@maZahaca
Copy link
Member Author

@eddiejaoude I think the issue was resolved and two records were connected, at least from a data perspective.

image

@eddiejaoude
Copy link
Member

Good spot! Yes I manually combined those 2 repos 👍 this will still be an issue in the future for other repos, so I will keep the issue open for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠 goal: fix 🚦 status: awaiting triage Waiting for maintainers to verify (please do not start work on this yet)
Projects
None yet
Development

No branches or pull requests

2 participants