Branch Reminder
A VS Code extension that reminds you to check which Git branch you're working on.
What it does
- When you open a folder that has a Git repo, it shows a message: "Hey, check which branch you're working on" and tells you the current branch name.
- You can run the reminder anytime via the Command Palette.
How to run it
Option 1: Run from source (no install)
- Open this folder in VS Code.
- Press
F5 or go to Run > Start Debugging.
- A new VS Code window opens with the extension loaded. Open a folder that has a Git repo — you’ll see the branch reminder.
Option 2: Install as a local extension
- In VS Code, open the Command Palette (
Cmd+Shift+P / Ctrl+Shift+P).
- Run Extensions: Install from VSIX… (or pack the extension first, see below).
- To pack: from this folder run
npx @vscode/vsce package
then install the generated .vsix file.
Commands
- Branch Reminder: Check which branch you're on — Shows the reminder and current branch (Command Palette).
Requirements
- VS Code 1.85 or newer (or Cursor)
- A workspace that contains a Git repository (the built-in Git extension is used to read the branch).
How to publish online
1. Fix package.json first
- Replace
YOUR_PUBLISHER_ID with your publisher name (e.g. your GitHub username or a name you choose). This must be unique on the marketplace.
- Replace
https://github.com/YOUR_USERNAME/alienx with your real repo URL if you push the code to GitHub.
npm install -g @vscode/vsce
3. Create a publisher (one-time)
VS Code Marketplace (marketplace.visualstudio.com):
- Go to Visual Studio Marketplace – Publishers.
- Sign in with your Microsoft account.
- Click Create Publisher and pick the same Publisher ID you put in
package.json.
Open VSX (for Cursor and other editors):
- Go to open-vsx.org and sign in (e.g. with GitHub).
- Go to your profile and create a namespace — use the same name as your publisher ID.
4. Log in and publish
VS Code Marketplace:
cd /path/to/ext
vsce login YOUR_PUBLISHER_ID
vsce publish
Open VSX (so it works in Cursor):
npm install -g ovsx
ovsx create-namespace YOUR_PUBLISHER_ID # if needed
ovsx publish -p YOUR_OPENVSX_TOKEN
Get a token from: Open VSX → profile → Access Tokens.
5. After publishing
- VS Code / Cursor: Users can search for AlienX in Extensions and install.
- Updates: Bump
version in package.json, then run vsce publish or ovsx publish again.
| |