Ship and undo
Shipping is accepting a pull. The change merges into main and the app goes live with it.
Ship
Open the pull, look at its preview, check that its test result is green, and press Merge. Or from a terminal:
forge ship 3
It shows the pull and its check, asks Ship #3? [y/N], and merges. Add --yes to skip the question. The forge's rules stay in force: a red check or a conflict refuses the merge and says why.
Look before you ship
- The preview is a real running copy of the app with the change in it.
forge pullslists the open pulls and their checks.- A pull you do not like can be answered in words: tell the crew what to change, and it updates the same pull.
Undo
Nothing is lost when you ship: every version is in the git history.
- Ask the crew:
forge tell "undo what pull 3 changed". It opens a new pull that reverses it, and you ship that. - Or do it yourself in your clone:
git revertthe merge commit, thengit push origin HEAD:main.
Undo is itself a pull or a push, so it is checked and deployed like any other change.
Hold
If you are not ready, leave the pull open: it stays previewed and nothing changes in production.
Reference: pulls, apps, cloning over git. Next: Your apps.
Every feature note, by topic: the reference notes.