GitAcc

VS Code extension for managing multiple Git identities. Register accounts, pick one before each commit, and review or edit commit history from Source Control.

Why GitAcc?

If you work with personal and professional Git accounts in the same editor, GitAcc keeps identities organized and asks which account to use before the native Git commit flow continues (stage-all prompt, commit message, etc.).

Features

Installation

1. Open Extensions (Ctrl+Shift+X / Cmd+Shift+X)
2. Install GitAcc (or load this folder with Run Extension / F5)
3. Open GitAcc in the activity bar to add accounts

Quick start

1. Add accounts

1. Open GitAcc → Accounts
2. Click Add account
3. Set a short label (e.g. Work, Personal), full name, and email

Manage options under GitAcc → Settings in the sidebar.

2. Switch account

• Click an account in the sidebar
• Click the footer (status bar) item
• Click the account icon in the SCM toolbar
• Use GitAcc: Switch Account from the Command Palette

The active account is applied to git config (user.name / user.email) according to Apply scope.

3. Commit with account selection

With gitacc.promptOnCommit enabled (default):

1. Click Commit in Source Control (or Cmd/Ctrl+Enter in the commit input)
2. If you have more than one account, choose Account for this commit
3. Continue with the normal Git flow

With a single account, GitAcc uses it automatically. With promptOnCommit off, the active account is applied without showing the picker.

{
  "gitacc.promptOnCommit": false
}

4. GitAcc commit view

In Source Control, expand the GitAcc section:

• Commit list refreshes after commits, push, pull, and other repo changes
• Expand a commit → changed files
• Click a file → side-by-side diff
• Right-click a commit:
  • Change Author · Edit Message · Edit Date
  • Undo Commit · Remove from Git
  • Copy Hash · Copy Message
• Multi-select commits (Cmd/Ctrl + click) → Bulk Change Author

5. Footer (status bar)

When enabled, shows: [icon] GitAcc Label (e.g. GitAcc TSE).

Click to switch account. Active state uses a configurable theme color and prominent background.

Sidebar settings

Expand GitAcc → Settings:

Settings (VS Code)

All options are also in Settings → GitAcc.

Example configuration

{
  "gitacc.accountsSource": "workspace",
  "gitacc.promptOnCommit": true,
  "gitacc.showInStatusBar": true,
  "gitacc.statusBarIcon": "person",
  "gitacc.statusBarActiveColor": "charts.green",
  "gitacc.applyScope": "local"
}

Data storage

User file (default)

~/.gitacc/accounts.json

Workspace file (project root)

.gitacc.json

Create or open from GitAcc → Settings → Create workspace JSON.

When created, GitAcc adds .gitacc.json to .gitignore automatically. Remove workspace JSON deletes the file and removes that line from .gitignore (and deletes .gitignore if it becomes empty).

Both files use the same format:

{
  "activeAccountId": "uuid",
  "accounts": [
    {
      "id": "uuid",
      "label": "Work",
      "name": "Your Name",
      "email": "you@company.com"
    }
  ]
}

Accounts source (gitacc.accountsSource)

Merge rule: if the user file has more accounts than the workspace file, the workspace file is ignored and only user accounts are used. Otherwise accounts are merged by email (user entries win on duplicates).

Use workspace when the project defines its own accounts in .gitacc.json. Use merge to combine team templates with personal accounts in ~/.gitacc/accounts.json.

Reset data

GitAcc → Settings → Reset data (or GitAcc: Reset GitAcc Data):

Each destructive action asks for confirmation.

Commands

Requirements

• VS Code 1.100+
• Built-in Git extension (vscode.git)
• Git on PATH

Limitations

GitAcc only sets user.name and user.email. It does not manage GitHub/GitLab login, tokens, SSH keys, or GPG signing.

Author

Heber Almeida — github.com/heberalmeida

License

MIT