Item logo image for LeetPush β€” LeetCode to GitHub Auto-Pusher

LeetPush β€” LeetCode to GitHub Auto-Pusher

4.9(

7 ratings

)
ExtensionTools5 users
Item media 4 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 1 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 2 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 3 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 4 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 1 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 1 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 2 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 3 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher
Item media 4 (screenshot) for LeetPush β€” LeetCode to GitHub Auto-Pusher

Overview

Automatically sync accepted LeetCode submissions directly to your GitHub repository with zero friction.

πŸš€ LeetPush β€” Automatically Sync LeetCode Solutions to GitHub with Zero Friction! Stop manually copying and pasting your code after solving problems. LeetPush seamlessly connects your daily LeetCode practice with your GitHub portfolio. The moment your solution receives an "Accepted" verdict, LeetPush extracts your exact submitted code and commits it directly to your GitHub repository in an organized, multi-language folder structure. ⚑ KEY FEATURES β€’ πŸš€ Instant Automatic Sync: Solutions are pushed to your GitHub repo the second LeetCode confirms an "Accepted" verdict. β€’ 🎯 Exact Submission Extraction: Captures the precise accepted code directly from network responses (no draft editor mistakes). β€’ πŸ›‘οΈ Anti-Duplicate Fingerprinting: Uses SHA-256 hashes (slug + language + code) so repeated submissions or duplicate clicks never pollute your Git commit history. β€’ πŸ“ Clean Organized Architecture: Automatically organizes solutions by problem name with code files and optional formatted problem READMEs with difficulty badges. β€’ πŸ”’ 100% Client-Side & Private: Runs directly in your browser. Your GitHub token stays strictly inside Chrome's private local storage. No middleman servers or third-party tracking. β€’ πŸŽ›οΈ Minimalist Glassmorphic UI: In-page floating status pill on LeetCode, quick-action popup, and full options configuration. ===================================================================== πŸ”‘ HOW TO GENERATE YOUR GITHUB ACCESS TOKEN (WITH ADMIN PERMISSION) ===================================================================== To allow LeetPush to push code and create files in your GitHub repository, you need a Personal Access Token. Follow these simple steps: OPTION 1: CLASSIC TOKEN (Fastest & Recommended β€” 30 Seconds) 1. Log in to GitHub (https://github.com). 2. Click your Profile Picture in the top-right corner βž” "Settings". 3. Scroll down the left sidebar to the very bottom and click "Developer settings". 4. In the left menu, click "Personal access tokens" βž” "Tokens (classic)". 5. Click "Generate new token" βž” "Generate new token (classic)". 6. Set "Note" to: LeetPush 7. Set "Expiration" to: 90 days (or No expiration). 8. Select Permissions / Scopes: β€’ [βœ“] repo (Check the main "repo" box β€” this grants full control of private/public repositories to commit and push code). β€’ [βœ“] admin:repo_hook (Check this to add full admin control of repository hooks). β€’ [βœ“] admin:org (Check this ONLY if your target repo belongs to a GitHub Organization and you need admin rights). 9. Scroll to the bottom and click "Generate token". 10. Copy the generated token immediately (starts with "ghp_..."). Keep it safe because GitHub will only show it once! --- OPTION 2: FINE-GRAINED TOKEN (Granular Repository Scopes) 1. Go to GitHub Settings βž” Developer settings βž” Personal access tokens βž” "Fine-grained tokens". 2. Click "Generate new token". 3. Name it "LeetPush" and choose your expiration. 4. Under "Repository access", choose "Only select repositories" and select your LeetCode practice repository. 5. Under "Permissions", expand "Repository permissions": β€’ Administration: Change dropdown to "Access: Read and write" (Grants full Admin permissions). β€’ Contents: Change dropdown to "Access: Read and write" (Required to commit and create code/README files). β€’ Metadata: Automatically set to "Read-only". 6. Click "Generate token" at the bottom and copy your token (starts with "github_pat_..."). ============================================================ πŸš€ HOW TO USE LEETPUSH (3 EASY STEPS) ============================================================ 1. Click the LeetPush icon in your Chrome extensions toolbar. 2. In the GitHub Repository field, enter your repository name: username/repository-name (e.g., JohnDoe/leetcode-solutions) 3. Paste your generated GitHub Personal Access Token and click "Connect & Save". That's it! Now go to any problem on LeetCode (leetcode.com/problems/). Solve the problem and hit Submit. Once you see "Accepted", LeetPush will instantly push your solution to GitHub! ============================================================ πŸ”’ PRIVACY & SECURITY FIRST ============================================================ β€’ Zero Telemetry & Analytics: We do not track, collect, or store any of your data. β€’ Direct GitHub Communication: All requests travel securely from your browser directly to api.github.com. β€’ Open Source & Transparent: 100% open source and verifiable on GitHub. Open Source Repository: https://github.com/RIKKY-J/LeetPush

Details

  • Version
    1.0.0
  • Updated
    October 12, 2026
  • Offered by
    Rikky Jakhar
  • Size
    51.25KiB
  • Languages
    English
  • Developer
    L-1 New Delhi, Delhi 110059 IN
    Email
    rikkyj108@gmail.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization
The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps