.gitbay/wiki/FAQ.org

FAQ

Where do I log in?

You do not, for most things. The web is read (and light write) — mint a browser session with gitbay web login.

Pull requests?

Merge requests: gitbay mr create from a branch or fork; merges are ff/merge/squash/rebase with signature policy.

Stacked PRs?

Target another open merge request's source branch. The forge reads the stack from the branches, retargets what is above when the one below merges, and refuses squash or rebase under a stack. No stack command; the workflow is branches. See Stacked merge requests.

Moving from GitHub?

gitbay repo import (git data) then gitbay repo import-issues (history); repo mirror covers the transition window.

What is not planned?

A container or package registry (scope creep away from "forge"; external registries integrate through CI), an email patch flow (revisit only if sourcehut-style demand appears), federation and Postgres (no need at this scale). Recorded so the absence reads as a decision, not an oversight.

Does CI run for my repository on gitbay.org?

Not yet. The runner there is scoped to the forge's own repositories and its isolation canary, since it shares the host with the forge. A .gitbay/ci.yml in your repository queues builds nothing claims. krz/gitbay#184 is where that gets decided. A self-hosted instance runs the same runner for whichever repositories its operator names.