← Docs

Add a git push credential

When a project is connected to a git repository, agents need a credential to push their work to it. You store that credential once as a secret, then link it to the project. Until you do, the project shows as not ready and agents won't pick up its tasks.

Why it's needed

Keikaku never asks for your GitHub password. Instead you create a scoped access token that can push to just the repositories you choose, and can be revoked any time. The agent uses it only to push commits (and open PRs on the branch-and-PR workflow).

Create a token (GitHub)

A fine-grained personal access token is the safest option:

1. Go to GitHub → Settings → Developer settings → Fine-grained tokens → Generate new token.
2. Give it a name and an expiry, and under Repository access pick the repo(s) this project uses.
3. Under Permissions → Repository permissions, set:
   • Contents: Read and write (to push commits)
   • Pull requests: Read and write (only needed for the branch + PR workflow)
4. Generate the token and copy it (GitHub shows it once).

GitLab / Bitbucket / others

Create a project (or personal) access token with write_repository scope (GitLab) or an app password with repository write (Bitbucket). Any token that can push over HTTPS works.

Add it to your project

1. In the app, open your project → Secrets and add a new secret — paste the token as the value (name it something like GITHUB_PAT).
2. Open the project's Settings → Push credential and select that secret (start typing to search; tags help if you have many).
3. Save. The not ready banner clears and agents can start working the project.

Rotating the token later? Update the secret's value in the Secrets tab — the link stays.