[gopikrishnamahalingam]

Summary

• Add a "Most open issues" option to the Sort dropdown.
• Sort issues by their project's open issue count in descending order.
• Preserve the selected sort option in the URL so it survives page reloads.

Testing

• Tested locally using python3 -m http.server -d site.
• Verified sorting order and URL persistence.

Closes #215

• I didn't edit generated files (issues/by-*, data/, site/data/, the README stats block).
• For pipeline changes, python3 -m unittest discover scripts, ruff check scripts and ruff format --check scripts pass.

[gopikrishnamahalingam]

I didn't knew that we need to change i18n file for all translations. I thought I only need to add once. Upon the error shown up during checks. I gave the error to ChatGPT and it told me to add relevant translations. I added those and committed the recently changed i18n file.

[TanbirRamim]

Merged, thanks @gopikrishnamahalingam! Small follow-up in #296: a repo without open_count now counts as 0 instead of sorting on NaN, and ties fall back to last update like the other sorts. On your question in #215: those fallbacks are tie-breakers, so equal stars or comments still get a stable, sensible order. If the radar was useful to you, a star helps other newcomers find it.

[gopikrishnamahalingam]

Thank you so much for the clarification. It does make sense to use fallbacks there. I didn't knew that we could even add tie-breakers. and also I will keep this in mind the next time that I need to also think about the edge cases. Thanks again for the explanation.