Source version control
Where Koda opens pull requests: GitHub, GitLab, Azure DevOps, Bitbucket and AWS CodeCommit.
Providers
With an access token saved for the provider and organization, Koda creates the pull request itself. Without one, it pushes the branch and opens the provider's page.
Source version control
Access tokens by provider and organization, and pull request defaults.
Adding a provider
Pick the provider, type the organization and paste an access token, then click Save. KodaCode keeps the token in the OS keychain, never in the config file.
| Provider | Organization field | Access token |
|---|---|---|
| GitHub, GitHub Enterprise | Organization or user. Leave it empty for a token that covers every one. | A personal access token with pull request write access. A fine-grained token covers one owner and cannot open a pull request on a repository where you are not a member. Use a classic token for that. |
| GitLab, GitLab self-managed | Group. Leave it empty for a token that covers the whole server. | A personal access token with the api scope |
| Azure DevOps | Organization | A personal access token with Code read and write |
| Bitbucket | Workspace | A repository, project or workspace access token, or an API token, with pull request write access. App passwords no longer work. |
| AWS CodeCommit | Region. Leave it empty for every region. | An access key, as ACCESS_KEY_ID:SECRET_ACCESS_KEY. Add :SESSION_TOKEN for a temporary key. |
GitHub Enterprise and GitLab self-managed also ask for the server's address.
For a pull request, KodaCode uses the token saved for the remote's own organization. If there is none, it uses a token saved for the whole provider. Without either, KodaCode pushes the branch and opens the provider's new pull request page in your browser. Pushing uses the git credentials you already have for the remote.
Config keys
The settings are in [source_control] in config.toml: connections (each with kind, server and owner), draft and branch_prefix.