Bug: Leaderboard workflow fails on protected branch repositories

[Harxhit]

Description

The contributor leaderboard workflow currently generates and commits leaderboard.json successfully, but fails when attempting to push changes directly to the protected main branch.

Repository branch protection rules require all changes to go through a pull request, causing the workflow to fail with:

remote: GH013: Repository rule violations found
remote: Changes must be made through a pull request.

Current Behavior

1. Workflow generates apps/web/public/leaderboard.json
2. Creates a commit successfully
3. Attempts to push directly to main
4. Push is rejected by branch protection rules

Expected Behavior

The workflow should comply with repository rules by:

• Creating a pull request automatically for leaderboard updates, or
• Using an alternative update mechanism that respects branch protection policies

Impact

The leaderboard data is generated successfully but never reaches the repository, causing the automation to fail on every scheduled run.

Suggested Solution

Update the workflow to create a dedicated branch and open a pull request for leaderboard updates instead of pushing directly to main.

Additional Context

The path-related issue has already been resolved. The remaining failure is caused by repository rules preventing direct pushes to protected branches.

[ramnnn2006]

hi @Harxhit , i'd like to work on this issue.

The problem is that direct git pushes to main are blocked by branch protection rules. I plan to fix this by:

• Changing the pull-requests permission in the leaderboard.yml workflow to write.
• Replacing the direct git push step with the peter-evans/create-pull-request action. This will create a pull request from a branch like automation/leaderboard-update when the JSON updates, and it will update the same PR on subsequent runs to avoid creating multiple PRs.

Let me know if you need any other details, and please assign this to me if the approach looks good.

[Harxhit]

@ramnnn2006 I have assigned this issue to you.

[ramnnn2006]

@Harxhit i've made the pull request.