Skip to content

README.en.md

Latest commit

 

History

History
117 lines (85 loc) · 3.55 KB

README.en.md

File metadata and controls

117 lines (85 loc) · 3.55 KB

AlgorithmHub

license release chrome web store

A Chrome extension that automatically syncs accepted LeetCode, Programmers, and HackerRank submissions to GitHub.

한국어 · Issues

What Is AlgorithmHub?

AlgorithmHub is a Chrome extension for people who want to keep their coding practice repository up to date without manually copying files after every accepted submission.

It connects your GitHub repository and automatically saves accepted solutions from:

  • LeetCode
  • Programmers
  • HackerRank

Highlights

  • Sync accepted submissions directly to GitHub
  • Use one extension for LeetCode, Programmers, and HackerRank
  • Create a new repository or connect an existing one
  • Customize repository path templates by platform
  • Keep a clean root README with platform-based summary

How does AlgorithmHub work?

  1. Connect your GitHub account and repository
  2. Solve a problem on LeetCode, Programmers, or HackerRank
  3. Submit an accepted solution
  4. Let AlgorithmHub sync the solution files to GitHub automatically
LeetCode Demo Programmers Demo HackerRank Demo
LeetCode demo Programmers demo HackerRank demo

Usage

  1. Open the extension popup
  2. Authenticate with GitHub
  3. Create a repository or connect an existing one
  4. Solve a problem on LeetCode, Programmers, or HackerRank
  5. Submit an accepted solution
  6. Let AlgorithmHub sync it to GitHub

How to Set Up AlgorithmHub for Local Development

npm install
npm run build
npm run lint

Then in Chrome:

  1. Open chrome://extensions
  2. Turn on Developer mode
  3. Click Load unpacked
  4. Select the dist/ directory

Contributing

Contributions are welcome.

If you want to improve AlgorithmHub, you can contribute by reporting bugs, requesting features, or opening pull requests.

Issue Guide

  • Create an issue before starting larger changes
  • Use these prefixes for issue titles:
    • bug: for bug reports
    • feat: for feature requests
  • Include reproduction steps, expected behavior, and screenshots when relevant

Pull Request Guide

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Run npm run lint and npm run build
  5. Open a pull request with a clear summary
  6. Link the related issue if one exists

Use these prefixes for pull request titles:

  • fix: for bug fixes
  • feat: for new features
  • chore: for maintenance, cleanup, and non-user-facing updates

Issues

If you found a bug or want to request a feature, open an issue:

Inspired by