The SolveBase setup guide

How do I save coding solutions to GitHub automatically?

Install SolveBase, choose a public repository and your coding platforms, then connect GitHub. Submit solutions as usual with the extension active. SolveBase saves newly accepted solutions and updates your repository README automatically.

Install SolveBase free

What is SolveBase?

SolveBase is a free Chrome extension that automatically saves newly accepted Codeforces, LeetCode, CSES, CodeChef, and GeeksforGeeks solutions to a public GitHub repository.

It captures new submissions while active. It does not bulk-import old submission history. Source code travels directly from your extension to GitHub; SolveBase's backend handles the GitHub authorization exchange.

Created by Tushal Lohar. Read the source code and technical documentation or the privacy policy.

Set up SolveBase in four steps

  1. Install and open SolveBase

    Install SolveBase from the Chrome Web Store, then open its popup from your browser's extensions menu. Use Chrome 112 or later, or a compatible Chromium-based browser.

  2. Choose your repository and platforms

    Enter a repository name, enable the platforms you use, and fill in the requested usernames. Confirm that the repository and committed solutions will be public.

  3. Connect GitHub

    Select Connect GitHub and authorize SolveBase. It creates a public repository if the name is available, or connects a compatible existing public solutions repository. No personal access token or separate SolveBase account is required.

  4. Submit a solution and check GitHub

    Stay signed in to your coding platform and submit a solution on a supported page while the extension is active. After the final accepted verdict, check your repository for the solution file and updated README summary. Codeforces pretests must finish system testing first.

Which pages and platforms are supported?

SolveBase 1.0.0 platform support and GitHub folder organization
PlatformSupported pagesOrganized by
CodeforcesContest and practice submissionsProblem rating
LeetCodeStandard leetcode.com/problems/ pages; excludes contest and Explore editorsProblem topic
CSESProblem set tasks and resultsProblem set section
CodeChefProblem and submission pagesProblem rating
GeeksforGeeksPractice problemsProblem difficulty

Setup and troubleshooting questions

Why does SolveBase ask me to confirm that my solutions will be public?

SolveBase supports public GitHub repositories only. Anyone can read solutions committed to a public repository. The setup confirmation makes this visibility explicit before GitHub is connected; private repositories are not supported.

What GitHub permissions does SolveBase request?

SolveBase uses GitHub OAuth with the public_repo scope to create and update public repositories. This permission applies to public repositories on your account, although SolveBase uses the repository you select. You do not need to create or paste a personal access token. You can revoke access in GitHub Settings under Applications.

Why has my accepted solution not appeared in GitHub?

Check that SolveBase is enabled, the platform is selected, your requested username is correct, and you are signed in to the coding platform. Confirm that you submitted on a supported page and that GitHub is connected in the extension popup. Codeforces pretests are not a final accepted verdict. Accepted solutions that fail to reach GitHub can be retried locally for up to 24 hours; reconnect GitHub if the extension requests it.

What happens if I reconnect GitHub or change repositories?

Reconnecting the same GitHub account and repository preserves pending submissions. Changing the GitHub account or repository clears the old work queue. Files already committed to GitHub remain in the original repository.

What happens when I solve the same problem again?

SolveBase updates the existing solution file instead of counting the problem twice. Recognized files from an existing solutions repository keep their folder and filename stem; if the solution language changes, the file extension changes to match.

Will SolveBase overwrite my existing README?

SolveBase updates its marked summary block and preserves README content outside that block. When you connect a compatible public solutions repository, it rebuilds its local index from recognized platform folders and solution filenames. Unrecognized scratch files are ignored, and unrelated non-empty repositories are rejected.

Still having trouble? Open a support issue with the platform, extension version, expected behavior, and error message. Omit tokens and secrets.