#+title: 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-MRs][Stacked merge requests]].
- Moving from GitHub or Codeberg? :: =gitbay repo import= (git data)
  then =gitbay repo import-issues= (history, from GitHub or any Forgejo
  =--api-base=); =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? :: On a runner you
  attach. The instance's own runner builds the forge's repositories and
  its isolation canary, since it shares the host with the forge.
  Install =gitbay-runner= on a machine of yours, run =gitbay-runner
  init=, and attach the key it prints with =repo runner add= or on the
  repository's settings page; see the Users page. A self-hosted
  instance can do the same, or run one runner for whichever
  repositories its operator attaches it to.