The top earners calculation now prioritizes GitHub issue payments (p2p_amount_usd) for users with linked paid issues, falling back to the existing winnings field otherwise.

Changes

Query Logic (website/views/core.py)

• Annotate UserProfile with aggregated github_earnings from GitHubIssue.p2p_amount_usd
• Use Case/When to select GitHub payments when present, otherwise winnings
• Filter by total_earnings > 0 to exclude zero-balance users

Template (website/templates/home.html)

• Display total_earnings annotation instead of winnings field

Tests (website/tests/test_core.py)

• Verify GitHub payments are summed correctly across multiple issues
• Verify fallback to winnings when no paid GitHub issues exist
• Verify mixed scenarios (paid issues vs winnings-only users)

Example

top_earners = (
    UserProfile.objects.annotate(
        github_earnings=Coalesce(
            Sum("github_issues__p2p_amount_usd", 
                filter=Q(github_issues__p2p_amount_usd__isnull=False)),
            Value(0),
            output_field=DecimalField(),
        ),
        has_github_issues=Count("github_issues", 
            filter=Q(github_issues__p2p_amount_usd__isnull=False)),
        total_earnings=Case(
            When(has_github_issues__gt=0, then=F("github_earnings")),
            default=Coalesce(F("winnings"), Value(0)),
        ),
    )
    .filter(total_earnings__gt=0)
    .order_by("-total_earnings")[:5]
)

Users with paid GitHub issues display aggregated payment amounts. Users without paid issues continue displaying their winnings field value unchanged.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.