Personal Workspaces

What a personal workspace is

A personal workspace scores the work you do outside your company's repositories: open source contributions, side projects, and pull requests you've merged on other people's public repos. It's yours alone. Your company workspace keeps working as before, and you switch between the two from the same menu.

It lets you see the engineering in all the code you ship, including work your company workspace never sees, and follow your AI multiplier across all of it.

Personal workspaces work with GitHub only.

If you already use GitVelocity at work

If you already belong to a company workspace, you don't need another account.

  1. Click your workspace name at the top of the sidebar to open the workspace menu, and choose Create personal workspace.
  2. In the Create your personal workspace dialog, click Create and verify GitHub login. GitVelocity creates the workspace, switches you to it, and sends you to GitHub.
  3. Sign in to GitHub with the account your own work is on. It can be your work account or a different one; see Which GitHub account goes where.
  4. Add your own model key under Settings → AI Scoring. Your company's key is never used here.
  5. Bring in your work.

Each person gets one personal workspace. Once you have it, Create personal workspace disappears from the menu, and the workspace sits in the same list as your company workspace, marked Personal. Nothing in your company workspace changes. Switch back from the menu at any time.

While you're in your personal workspace, a banner names your company workspace and offers Switch. If you dismiss it, it stays hidden in that browser until you join another company workspace.

New to GitVelocity

If your company isn't on GitVelocity yet, or nobody who can install GitHub apps is around to help:

  1. Under What do you want to measure?, choose Just my own work.
  2. Sign in with GitHub to confirm which GitHub account is yours.
  3. Add your own model key under Settings → AI Scoring.
  4. Bring in your work.

If you want to measure your team instead, choose My team's repos and follow Connecting Your Repositories. If you've already asked your GitHub organization's owners to install the app, While you wait, start with your own work sets up a personal workspace for you in the meantime; see When you are not a GitHub organization owner.

Bringing in your work

A new personal workspace starts empty. Its dashboard offers the first two ways below under Start measuring your own work, and the third runs from your terminal. You can use any combination of them.

Import your public work

Most of your visible work may be merged pull requests on other people's public repos, such as your employer's open source projects or upstream libraries. You can score those without installing anything:

  1. On your personal dashboard, find Your public work and click Import my public work. GitVelocity searches GitHub for your merged pull requests on public repos from the last 24 months and scores up to 500 of them per import with your model key.
  2. The card shows how many pull requests were found, scored, skipped and failed. It also says why any were skipped: bot accounts, your own forks, pull requests already scored, diffs with nothing left to score once excluded files are dropped, and diffs too large for GitHub to serve in full. A skipped pull request would be skipped again, so there is nothing to retry. Failed counts only real errors, and Refresh PRs tries those again. Large diffs that GitHub does serve are scored on their first part and reported as truncated.
  3. After that, the card checks GitHub for you (a free search, at most once an hour) and shows what Refresh PRs would pick up: the pull requests merged since your last import that aren't scored yet, any that failed and will be retried, and an estimate of what scoring them costs on your model key, for example "3 new, 1 to retry · ~$0.40". The estimate is the average cost of your recent scored pull requests. Nothing is scored until you click. When there's nothing new and your earlier imports left nothing behind, the card says it's up to date since your last import.

Only one import runs at a time. If an import finds nothing, the card says so and suggests importing older work. To reach back further than 24 months, see Your baseline.

Your public contributions appear on the Activity page under Your contributions to other repos, one row per repo. Click Exclude on a repo to take its scores out of your multiplier and dashboard. The scores are kept, so Include brings them back.

Install the app on your personal GitHub account

To score repos that live on your own GitHub account, choose Add my personal repos and install the GitVelocity GitHub App on your personal account. You can install it only on your own account. From then on, pull requests merged in those repos are scored as they merge. To score their older history, use Settings → Historical Backfill.

Pull requests other people merge into those repos are scored too, on your key, but your dashboard shows only your own.

Score cloned repos with gv score

The GitVelocity CLI scores the changes you authored in a repo you have cloned. It runs on your machine with your own model key, and it's meant for repos you can read but can't connect to GitVelocity. GitVelocity receives the scores, the model's notes on each change and its size, never the diff or your code.

These scores show a Scored locally badge, and a local score never replaces one GitVelocity computed itself. Changes that aren't part of a pull request are stored as commits. If you score repos that belong to your employer, check that your company allows sending its code to the model provider you use.

What you see

The personal dashboard is about you only. It shows:

  • Your AI multiplier: how your monthly points compare with your baseline.
  • How you stack up: a map of you and the open source engineers whose points are closest to yours. It fills in once you have at least three scored pull requests in the last six months.
  • Engineers like you: the same people as a list. Click one to see their scored public pull requests.

Leaderboards, Benchmarks and the team settings are hidden, since there's no team to rank or compare.

Your baseline

Your AI multiplier needs a baseline: your first three full months with at least 3 merged changes. Until you have one, the multiplier card says No baseline yet and names the months that already count. When the month in progress already has 3 merged changes, the card says it counts once it ends, or, if it would be your third month, that your baseline is set when it ends.

The card's Go back before button (for example, Go back before Oct 2024) imports your public work from the two years before your oldest import, which can turn up earlier months. Once you have a baseline, the same action is in the card's ⋮ menu. Imports reach back at most 60 months, and the card says so once you get there.

Personal and company workspaces

Which GitHub account goes where

Each workspace keeps its own GitHub login. GitVelocity always takes it from GitHub, so you never type one in.

  • Personal workspace: the account you sign in with when you create it, or the personal account you install the app on. GitVelocity doesn't copy it from your company workspace, so you sign in with GitHub again even if you've linked GitHub at work. It can be a different account from the one you use at work.
  • Company workspace: the account your company pull requests are matched to. If you join or create a company workspace on GitHub after verifying your personal login, and you have no login there yet, GitVelocity fills in your personal login for you. It never replaces a login you already have. If you joined through an install request you confirmed with a GitHub account, that account is used instead. Bitbucket and GitLab workspaces are never filled in this way.

If your work and personal GitHub accounts are different

If your company workspace picked up your personal login and your work pull requests come from a different account, change it there:

  1. Switch to your company workspace and open Settings → Profile.
  2. Under GitHub Account, click Unlink.
  3. Click Link GitHub Account and sign in with your work account. GitHub uses whichever account your browser is signed in to, so switch accounts on github.com first if you need to.

The same steps change the login of any workspace you're in, including your personal one.

What carries over

Nothing moves between workspaces. Scores, imports and gv score uploads stay in your personal workspace. Your company workspace scores your work from your company's repos and never sees your personal workspace. Leaving or deleting one doesn't touch the other.

Privacy

  • Only you can see your personal workspace, and nobody else can join it. It has no invites and no team settings.
  • Its scores are never counted in any benchmark or team ranking, and they never appear in your company workspace.
  • Scoring uses your own model key, never the platform's or your company's.
  • As with any workspace, code is processed for scoring and isn't stored afterwards. With gv score, your code never reaches GitVelocity at all.

To remove a personal workspace, delete it; see Leaving or Deleting an Organization.