LeetSync - Auto Push LeetCode to GitHub

Auto-push accepted LeetCode solutions to GitHub with study sheets, achievements and battle mode

LeetSync automatically pushes every accepted LeetCode solution to your own GitHub repository — the code, a README per problem, and an index that keeps itself up to date. Solve, submit, and it is committed. No copy-pasting, ever. ─── WHAT IT DOES ─── • Detects accepted submissions on leetcode.com and pushes them in seconds • Files each solution by problem number, with the right language extension • Re-submitting adds sol2, sol3… instead of overwriting your first attempt • Writes a README per problem: description, topics, your notes, your attempts • Keeps a root index with difficulty badges, language mix and a solve calendar • Queues and retries pushes that fail, so a dropped connection loses nothing ─── TWO COMPUTERS, ONE ACCOUNT ─── Sign in on a second machine with the same token and repo and it catches up by itself — same solved problems, same streak, same achievements, same sheet ticks. Solving on either keeps a single streak. Sign out publishes your progress first, so signing back in restores it. ─── STUDY SHEETS ─── Seven of the DSA sheets people actually work through are built in, covering 895 unique problems between them. Solving a problem ticks it off in every sheet it appears in, so one solve can advance four at once. Anything that is not a LeetCode problem you can tick by hand, and a full-page tracker gives you search and filters across all of them. ─── KEEPS YOU GOING ─── • Daily streak counter and a 90-day activity calendar • Achievements that unlock as you go • Battle mode — add a friend by GitHub username and compare progress • A public leaderboard — all-time, this week and today, scored Hard 10 / Medium 5 / Easy 3, which you join by switching usage reporting on • Every verdict recorded, so you can find the problems that took you 4 tries ─── TALK TO THE DEVELOPER ─── Settings has a box for feedback, an issue or a suggestion. It goes straight to the developer, and a reply comes back in the extension itself, quoted next to what you wrote — not into an inbox you have to go and check. ─── YOUR TOKEN, YOUR REPO ─── A classic personal access token with the repo scope lets setup finish in one click, because GitHub allows that kind to create the repository for you. If your solutions repo already exists, a fine-grained token limited to that one repository works too and is the safer choice — setup reads which kind you pasted and only asks the questions that kind can answer. The token is held in Chrome storage and sent only to api.github.com. It is never transmitted anywhere else, and you can revoke it on GitHub at any time. Installing asks for two websites and nothing else: leetcode.com, to read your accepted solution, and api.github.com, to commit it. Notifications and the reporting server are requested later, only if you turn those on. ─── PRIVACY ─── Usage reporting is optional. It is on unless you turn it off, you are shown the switch during setup, and Settings changes it at any time. It is also what puts your username and score on the public leaderboard; switch it off and you are not ranked. Sharing your solution code is a separate switch that stays off even then. One activity ping — a random ID and the version, twice a day at most — is on by default, disclosed at setup, and has its own switch. It does not record which tab you opened or that you opened the popup. Your GitHub token, repository name and GitHub username are never collected. Terms and conditions: https://leetsync-site.vercel.app/terms Privacy policy: https://github.com/Deveshsamant/LeetSync/blob/main/PRIVACY_POLICY.md Open source: https://github.com/Deveshsamant/LeetSync Website: https://leetsync-site.vercel.app/