.gitbay/wiki/FAQ.org

 1#+title: FAQ
 2
 3- Where do I log in? :: You do not, for most things. The web is read
 4  (and light write) — mint a browser session with =gitbay web login=.
 5- Pull requests? :: Merge requests: =gitbay mr create= from a branch or
 6  fork; merges are ff/merge/squash/rebase with signature policy.
 7- Stacked PRs? :: Target another open merge request's source branch.
 8  The forge reads the stack from the branches, retargets what is above
 9  when the one below merges, and refuses squash or rebase under a stack.
10  No stack command; the workflow is branches. See
11  [[Stacked-MRs][Stacked merge requests]].
12- Moving from GitHub? :: =gitbay repo import= (git data) then
13  =gitbay repo import-issues= (history); =repo mirror= covers the
14  transition window.
15- What is not planned? :: A container or package registry (scope creep
16  away from "forge"; external registries integrate through CI), an
17  email patch flow (revisit only if sourcehut-style demand appears),
18  federation and Postgres (no need at this scale). Recorded so the
19  absence reads as a decision, not an oversight.
20- Does CI run for my repository on gitbay.org? :: Not yet. The runner
21  there is scoped to the forge's own repositories and its isolation
22  canary, since it shares the host with the forge. A =.gitbay/ci.yml=
23  in your repository queues builds nothing claims. krz/gitbay#184 is
24  where that gets decided. A self-hosted instance runs the same runner
25  for whichever repositories its operator names.