👍 Top Issues Dashboard

[github-actions]

A simple dashboard that lists the top issues/bugs/features and pull requests.

Top issues

1. Let users request deletion of images #2891 👍17
2. How to differentiate US "Total carbohydrates" that include fiber from Europe "Carbohydrates" that exclude fiber #5675 👍5
3. Tag rules: Tag A + Tab B = Tag C #3426 👍5
4. Break down the Power User Script, and integrate individual features within Product Opener #5561 👍4
5. Add lactose support in ingredient analysis #4264 👍4
6. Big: Serving size is missing digits to strict #10961 👍3
7. Add a deep link to the Taxonomy Editor in the Ingredient analysis knowledge panel #9944 👍3
8. Create an API route to provide Quality Warnings and Errors on a given nutrition table/ingredients list #9710 👍3
9. Fix null value in various places: app, website, documentation, exports #9426 👍3
10. Mobile app: fine-tuning needed for 'image_to_update' #9226 👍3
11. Folksonomy Engine loads CSS and a font from CDNs #9012 👍3
12. Split Display.pm into API.pm and Frontend.pm, make frontend use the API #5205 👍3
13. Set up Sentry error reporting #3974 👍3
14. Knowledge panels for facet pages (tracker) #3824 👍3
15. Add a user mail / notifications / messages system #2552 👍3
16. Support EAN-13 for variable prices #1288 👍3
17. Remove circular dependencies in ProductOpener modules #622 👍3
18. Language switcher / selector should redirect to the same page in the chosen language when changing language #376 👍3
19. Allow moderators to delete a product from the product edit form #10705 👍2
20. Nutri-Score panel: add possible reasons when Nutri-Score(s) computed different than Nutri-Score on package #10387 👍2

Top PRs

1. feat: Implement OIDC sign-in #9251 👍2
2. refactor: Moosify ProductOpener::Nutriscore.pm #10007 👍1
3. fix: Migrated the JS from template form to real JS #9966 👍1
4. ci: CRON for packager codes #9295 👍1
5. feat: [WIP] Deep link to Hunger Games #5639 👍1

Created by the rickstaa/top-issues-action action (last update: 11/16/2024, 12:23:00 AM).

[teolemon]

@CharlesNepote "automated Quick Wins"

[CharlesNepote]

Yes great, @teolemon. The issue is that you have just one point per issue, but better done than perfect.

[rickstaa]

@teolemon First of all, thanks for trying out my action. I created it to better manage the issues in https://github.com/anuraghazra/github-readme-stats, but, amazingly, people are trying whether it also works for their projects. @CharlesNepote Feel free to create a feature request or pull request if you think the issue can still be improved 🚀.

[CharlesNepote]

@rickstaa thanks a lot for your nice project.

We have tried another method to sort issues: each participant has 100 credits quarterly and he can put them on the issue(s) he wants to. He can put 100 credits on one issue or allocate it on several issues. It allows the participants to express their priorities, which is not possible with the Github system (where all your "votes" are equal). The drawback of this method is that we need to do it by hand :(

I don't know if it's possible to parse Github issues' comments, but we could use a system where people would vote with a simple syntax, something like:
#My_credits_for_this_issue: 80
The parser might detect the hashtag and its corresponding amount, the user and the date of the comment. This way, it might be possible to establish a ranking based on people priorities. Do you think it's possible?

I have opened an issue on your repository: anuraghazra/github-readme-stats#2193

[rickstaa]

@CharlesNepote Thanks for your feature request. I could not migrate your issue to https://github.com/rickstaa/top-issues-action, so I made a reference and answered it on rickstaa/top-issues-action#94 (comment). If you have other suggestions on how we can implement this feature without hitting the problems described in that issue, feel free to comment 👍🏻.