Lab status: workforce rebuilding on measured foundations — qualification program runningread the audit →
KEEN LABS

GuidesCode

Connect GitHub, then commit and push from Code

Link a GitHub account to a Code workspace, pull the latest, commit your changes with a message, push, and open a pull request.

Draft · 7 steps unverifiedRevised 2026-08-18Open Code

Draft — not yet walked in the live product

All 7 steps below were written by reading the Keenoble source rather than by performing them, and each unwalked one is tagged [UNVERIFIED]. Reading a component tells you what a control is labelled; it does not prove the control is reachable, that the order is right, or that the result is what the text says. Until a reviewer has walked every step, this page is excluded from the sitemap, marked noindex, and publishes no structured data.

Before you start

  • A workspace open in Code, and a GitHub account you can authorise.

Steps

  1. Find the “Git” section in the Code sidebar, below the file tree. [Unverified]

  2. Click “Connect GitHub” and authorise in the window that opens. When it succeeds the panel shows your GitHub handle, with a small “reconnect” link beside it. [Unverified]

  3. Link a repository: click “Browse my repos” and choose one, or paste “github.com/owner/repo” into the box and click “Import from URL”. [Unverified]

    A workspace with no repository behind it is labelled “Local workspace (no repo linked)”.

  4. Before you start editing, click “↓ Pull from GitHub”. You get either “Already up to date” or a count of the files that changed. [Unverified]

  5. Edit your files. Once anything differs from the repository, a button appears reading “N changed files (commit)”. Click it. [Unverified]

  6. Type a commit message into “Commit message...”, then click “Commit + Push”. [Unverified]

    On success the panel reads “Pushed N file(s)”. With no edits it says “No changes to push”; without a GitHub connection it says “Connect GitHub first”.

  7. On a branch other than main, a “Create PR →” button appears. Use it to open a pull request; the panel then links it as “PR created — open in GitHub”. [Unverified]

Switching branches

The branch switcher sits under the repository name once you are connected. It knows whether you have unsaved changes, so switching is not a silent way to lose them.

The Connect button in Settings

Settings has an Account section with a GitHub row and a “Connect” button. As of 2026-08-18 that button is not wired to anything — connect from the Git panel in Code instead. We would rather say so here than let you press a button that does nothing.

Having problems with the platform? Contact us at support@keenlabs.pro. If a step here does not match what Keenoble does, the step is the bug — send it to the same address. All the guides are at /guides; shorter answers are on the FAQ.