Git & GitHub
Use KODEO as a Git remote
git clone, fetch and push against git.kodeo.website with the git you already have — credentials come from the kodeo CLI.
Every KODEO project with a repository can be cloned with plain git:
git clone https://git.kodeo.website/acme/storefrontCredentials
Run kodeo login once and accept its offer to set up git. From then on git asks kodeo for a password: a Git-only credential that lasts an hour and ends with your sign-in. Nothing long-lived is saved in ~/.git-credentials. In CI, use a personal access token with the Git scope as the password (the user name can be anything, e.g. kodeo).
What a push does
- To the branch the project is on: the files everyone sees change, like a checkout. People with the file open get your changes merged into their editor. If someone has uncommitted changes to a file your push touches, the push is refused with their name — ask them to commit first, or push to another branch.
- To any other branch: that branch moves; the project's files don't change.
- Force-pushing the project's current branch is refused. Branch policies (Team), repository size limits and the secret scan apply exactly as in the editor. To push a commit that looks like it holds a secret on purpose:
git push -o kodeo.allow-secrets.
Shallow clones (--depth 1) and partial clones (--filter=blob:none) work. KODEO's link to GitHub is separate — a local clone can have both remotes.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?