How can I automatically push my LeetCode solutions to GitHub after every accepted submission?

[shreyamishra4387-cmyk]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

API

Body

Hi everyone,

I'm looking for a way to automatically upload my LeetCode solutions to a GitHub repository whenever I solve and get an accepted submission.

My goal is:

• Automatically detect accepted LeetCode submissions.
• Commit the solution to a GitHub repository without manual intervention.
• Preserve the original filename and organize solutions by problem.
• Optionally include the problem statement and runtime/memory statistics in the commit.

I've explored browser extensions like LeetHub and LeetCode Sync, but I'm interested in understanding whether this can be implemented using GitHub APIs, webhooks, or another automation approach.

Some questions I have:

1. Does LeetCode provide any official API or webhook for accepted submissions?
2. If not, what is the most reliable way to automate this workflow?
3. Would GitHub Actions alone be sufficient, or is a browser extension or local script required?
4. Are there any recommended open-source projects for this purpose?

I'd appreciate recommendations on the most reliable and maintainable approach.

Thanks!

[abhitics]

The short answer is no—LeetCode does not provide an official public API or webhook that notifies GitHub when you solve a problem.

The most common approaches are:

1. LeetHub / LeetHub v2

   • Browser extension.
   • Automatically commits accepted solutions to GitHub.
   • Supports multiple programming languages.
   • No local setup required.

2. LeetCode Sync

   • Another browser extension with similar functionality.
   • Syncs accepted solutions to a GitHub repository.

3. Custom Automation

   • Use a browser userscript (Tampermonkey) or browser extension to detect accepted submissions.
   • Use the GitHub REST API to create commits.
   • Authenticate using a GitHub Personal Access Token (PAT).
   • This provides complete control over commit messages, folder structure, and metadata.

4. GitHub Actions

   • Useful for formatting code, updating the README, generating statistics, or validating commits.
   • However, GitHub Actions cannot detect new LeetCode submissions by themselves because GitHub has no way to know when you solve a problem.

If your goal is simply automatic syncing, LeetHub v2 is the easiest and most reliable solution.

If your goal is to build your own automation or learn GitHub APIs, then creating a browser extension or userscript that calls the GitHub REST API after an accepted submission is the recommended approach.