3 items
ShipIt: Push accepted LeetCode solutions to GitHub. ShipIt automatically detects when your LeetCode submission is Accepted and lets you push your solution to GitHub in one click. Stay Motivated! Celebrate each successful submission! Never lose track of your progress! Keep your GitHub history aligned with your LeetCode wins! What it does - Watches LeetCode problem pages for an Accepted result - Shows a lightweight toast: Push or Dismiss - On Push, ShipIt creates/updates a solution file in your GitHub repo (via GitHub’s official API) Setup (one-time) 1. Install ShipIt 2. Open ShipIt Settings 3. Add a GitHub token + repo info (below) Create a GitHub PAT (fine-grained) — step by step 1. Go to GitHub Settings 2. Open Developer settings 3. Click Personal access tokens → Fine-grained tokens 4. Click Generate new token 5. Set: - Token name: ShipIt - Repository access: Only select repositories → choose your target repo 6. Under Repository permissions, set: - Contents: Read and write - (Metadata is required by GitHub and stays read-only) 7. Click Generate token 8. Copy the token (you won’t see it again) and paste it into ShipIt Settings File format By default ShipIt writes solutions to: leetcode/{slug}/{slug}.{ext} Example: leetcode/two-sum/two-sum.py Privacy & security - Your GitHub token is stored locally in your browser using Chrome extension storage - ShipIt only talks to: - leetcode.com (to detect Accepted + read your editor) - api.github.com (to write the file you choose)
Feb 10, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.