Source Control in VS Code

With KODEO for VS Code, the Source Control view shows the project's own repository — the same one as KODEO's Source Control panel in the browser. There's no local .git involved.

No repository yet?

Choose Initialize Repository (at the top of Source Control, or in KODEO History). It starts Git for the whole project — you pick the first branch's name and whether to add a .gitignore. Or bring one in: KODEO Git: Clone from GitHub… takes any public repository by link (or one of yours); its files replace the project's, and the old ones go to the trash for 7 days.

What you see

• Your Staged Changes and Changes. Staging is per person: what you stage is yours, and what teammates have staged is shown as a note ("Ben has 2 staged"), never mixed into your list.
• Gutter bars and inline diffs in every file, against HEAD (or what you've staged).
• Inline blame — who last changed the line your cursor is on, and when, at the end of the line; hover it for the whole commit. (Only for files that match the last commit — with uncommitted edits the lines no longer match. Turn it off with the setting KODEO: Git Inline Blame.)
• KODEO History (in Source Control) — the commits on this branch, or on every branch; open one for the files it changed, and a file for its diff. Right-click a commit to copy its id, open it on GitHub, or make a branch or tag there; right-click a file to open it as it was, or restore that version. KODEO Git: File History (also on a file's right-click menu) shows just one file's commits.
• The branch in the status bar, and how far you are ahead of or behind GitHub.
• CI for the current commit in the status bar and in the Pull Requests & Checks view.
• The commit graph — KODEO Git: Show Commit Graph draws every branch as lanes; and KODEO Git: Toggle File Blame shows who changed every line of the file, shaded by age. See Pull request reviews, the commit graph and merges in VS Code.

Commit

Type a message and press Ctrl+Enter (or KODEO Git: Commit). If nothing is staged, you're asked whether to stage everything.

• People who edited the files with you are offered as co-authors (Co-authored-by: trailers) — untick anyone who didn't really help.
• Files open live are settled on the server first, so the commit holds exactly what's on screen.
• The secret scan runs like it does in the browser; sensitive paths (.env, keys) ask before they're staged.
• Commit & Push pushes to GitHub right after. Amend is refused once a commit has been pushed.

Branches, merges, stashes and tags

The … menu in Source Control has them all, grouped like VS Code's own Git (Branch · Stash · Tags · GitHub):

• Switch, create, rename and delete branches. In KODEO the branch belongs to the project, so switching changes it for everyone in the project — VS Code asks first. Uncommitted changes are parked on the branch they were made on and come back when you return. Switch Branch… also lists the linked GitHub repository's branches: pick one and it's fetched and checked out as a local branch.
• Merge Branch… merges another branch into the current one on KODEO. Conflicts appear under Merge Conflicts and in the files: use Accept Current / Incoming / Both above each conflict or Open in Merge Editor, stage each file (that marks it resolved) and commit — or Abort Merge.
• Branch rules (a Team can protect the default branch or require pull requests) are shown in the commit box and before a push — with the offer to create a branch instead. KODEO Git: Show Branch Rules lists them.
• A shallow clone's whole history: KODEO Git: Fetch the Full History.
• Stash your changes, then Pop, Apply or Drop a stash.
• Create Tag… (a message makes it annotated) and Delete Tag….

GitHub

Push, pull, fetch, Publish to GitHub, Link a GitHub Repository… and Unlink run on KODEO's server with your own GitHub connection. Your GitHub token never reaches VS Code. If GitHub isn't connected yet (or KODEO's GitHub App isn't installed where the repository lives), VS Code offers Connect GitHub (or Install KODEO's GitHub App): GitHub's own page opens in your browser — sign in, approve KODEO, pick the repositories — and VS Code carries on with what you asked for (Publish, push, a pull request…) by itself once you're done. You can cancel the wait any time. The browser has to be signed in to the same KODEO account; nothing else is needed.

Pull Requests & Checks lists open pull requests — click one to review it in VS Code (files, line comments, approve or request changes, merge, check out); KODEO Git: Create Pull Request… opens one from the current branch.

Things that need the browser

A few Git actions ask you to confirm it's you (a passkey or two-factor). VS Code can't do that step, so it offers to open KODEO in your browser for it. Branch protection policies (Team) are set there too.