Push the spec to a feature branch on your fork — that's all LiftOff needs. No pull request or merge required.
Push the OpenAPI Spec on a Feature Branch
You should still be on feature/deskly-collection from Part 2. You can commit the spec there, or create a dedicated branch — either works as long as the result lands on a feature/ branch.
-
Open the Postman terminal and confirm you're in your connected
deskly-apifolder. -
Option A — stay on the collection branch:
git checkout feature/deskly-collectionOption B — separate branch for the spec:
git checkout -b feature/deskly-openapi -
Review what changed:
git status -uExpect new or modified files under
postman/specs/(and possibly.postman/resources.yaml). -
Stage, commit, and push to your fork:
git add . git commit -m "Add Deskly API OpenAPI spec via Native Git" git push -u origin HEADUsing
HEADpushes whichever feature branch you're on — no need to type the branch name again.
That's enough for this module. LiftOff checks for an OpenAPI file under postman/specs/ on a feature/ branch in your fork.
Troubleshooting
postman/specs/missing fromgit status— generate the spec in Local View (Part 2), not Cloud View.- Push rejected — run
git pull --rebase origin feature/deskly-collection(or your current branch) and push again.