Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Forges

jj-release supports multiple forges for release creation and PR/MR opening:

Forgeforge =CLI requiredReleasePR/MRStatus
GitHub (default)"github"gh✓✓✓ tested
GitLab"gitlab"glab✓✓ (MR)✓ tested
Forgejo/Codeberg"forgejo"none (REST)✓✓✓ tested on Codeberg, release creation not yet supported (see note)
Gitea"gitea"none (REST)✓✓implemented, untested
None"none"––––

For GitLab, set forge_url if using a self-hosted instance:

[release]
forge = "gitlab"
forge_url = "https://gitlab.example.com"

For Forgejo/Codeberg, set forge_url to your instance and provide a token:

[release]
forge = "forgejo"
forge_url = "https://codeberg.org"
export FORGEJO_TOKEN=your-token

For Gitea, set forge_url to your instance and provide a token:

[release]
forge = "gitea"
forge_url = "https://gitea.com"
export GITEA_TOKEN=your-token

Note

Forgejo/Codeberg and Gitea: tagging, pushing, and PR creation all work correctly. create_release = true is not yet supported. The release API requires annotated git tags but jj creates lightweight tags. Keep create_release = false.

The token needs repository scope, create one at https://codeberg.org/user/settings/applications.

ForgeAuthentication
GitHubgh auth login locally or GITHUB_TOKEN in GitHub Actions
GitLabglab auth login locally or the token/env mechanism used by glab
ForgejoFORGEJO_TOKEN and forge_url
GiteaGITEA_TOKEN and forge_url