-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
twenty.com/contributors data inconsistencies #5715
Comments
Disclaimer: This comment was automatically generated with AI. It can give some useful hints as to where to look for, but sometimes it can also give very inaccurate answers so takes this with a pinch of salt :). To resolve the data inconsistencies for contributors on twenty.com, follow these steps:
Example code snippet to check merged PRs: const mergedPRs = prs.filter(pr => pr.state === 'merged'); Ensure this logic is applied consistently in both the sync and utility functions. References |
Hi! Can I start working on this? @Bonapara |
Sure @pacyL2K19, thanks for contributing! |
@FelixMalfait will be able to help! |
@sagarhedaoo, unfortunately, after discussing with the team, I realized we need to handle this issue internally since you won't be able to access the data locally. Perhaps you can take on another |
@Freebios would you mind looking into this? I think it's a prod issue (cron not running or something like that). But I don't know how to access the logs The cron should run this command I think: https://github.com/twentyhq/twenty/blob/main/packages/twenty-website/package.json#L11 |
@FelixMalfait the job seems to be running correctly, I do run this command every 5mn but I only get a successfull output :/ Could there be dirty data in database ? |
@thomtrp ran the command. It should be working now. Closing the issue! |
Description
Some contributors have an incorrect number of merged PRs displayed on their profiles.
For instance, @pacyL2K19 merged #5051 three weeks ago, but it is not shown as "Merged" on his profile.
The data from the comment we make when merging a PR also has some inconsistencies:
The text was updated successfully, but these errors were encountered: