Push and fetch

GitButler uses your system Git executable to authenticate with your remote. This means it uses the same SSH configuration, SSH agent, or credential helper as Git in your terminal.

Open your project settings, go to the Git section, and select Test credentials to verify that GitButler can push to the remote. The test pushes an existing commit to a temporary remote branch and removes the branch after the check.

If the test fails, configure authentication for your system Git first, then run the test again. GitButler no longer has separate settings for selecting an SSH key or credential helper.

Once authentication works, GitButler can automatically fetch upstream work and push new branches to your remote.

Land branches without pull requests

If your project does not review changes through pull requests, you can switch a project to the "push to main" workflow. During repository onboarding, check "Push to main / Skip pull requests mode". For an existing project, open the project settings, go to the Git section, and turn on "Land branches directly".

With this on, the "Create PR" button on the bottom branch of a stack becomes a "Land" button. Landing integrates the branch straight into the target branch — fast-forwarding when possible, otherwise with a merge commit — and pushes the result. It works without a forge integration.

Landing bypasses code review, CI checks, and branch protection, and a branch protected against direct pushes will reject it. The CLI equivalent is but land.