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.

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).
• 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.

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

Click the branch in the status bar (or KODEO Git: Switch Branch…). 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.

GitHub

Push, pull, fetch and Publish to GitHub run on KODEO's server with your own GitHub connection. Your GitHub token never reaches VS Code. Connect GitHub (or install KODEO's GitHub App) from KODEO in the browser, as usual.

Pull Requests & Checks lists open pull requests; 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.