feat: Algorithmic Tie-Breakers for Leaderboard Rankings (#192)

[nitishchaubeyy]

Description

Resolves #192 by implementing deterministic tie-breaking logic for the RankHer leaderboard. Previously, ties in totalPoints resulted in non-deterministic ranking orders.

Key Changes:

• Compound Sorting: Updated the Firestore query to include a hierarchical order: points.totalPoints (Primary) -> githubStats.commits (Secondary) -> githubUsername (Tertiary).
• Deterministic Results: This ensures that every time a user refreshes the page, the rank order remains consistent across all sessions, providing a stable UX.
• Index Requirement: Note that a new compound index is required in Firebase Firestore for this specific orderBy combination.

Fixes #192

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ranker-hub	Error		Jun 6, 2026 10:38am

[indresh404]

merge conflict

[nitishchaubeyy]

Done @indresh404

[indresh404]

Solve Merge Conflict

[indresh404]

Solve Merge Conflict

[nitishchaubeyy]

Done @indresh404

[indresh404]

If your PR still shows the old failed Vercel check, please rebase (or merge the latest main branch into your branch) and push again to trigger a fresh deployment/check run.

[nitishchaubeyy]

Hey @indresh404, I synced the branch with the latest main and pushed again to trigger the deployment. I also ran npm run build and npm run lint locally, and everything compiles perfectly without any errors on my end.

Since I don't have access to the Vercel logs, could you please check if it's failing due to a missing Environment Variable or a caching issue on Vercel's end?