Your progress is saved locally. to save it permanently.

0 of 1 steps0%

Push the spec to a feature branch on your fork — that's all LiftOff needs. No pull request or merge required.

1

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.

  1. Open the Postman terminal and confirm you're in your connected deskly-api folder.

  2. Option A — stay on the collection branch:

    git checkout feature/deskly-collection

    Option B — separate branch for the spec:

    git checkout -b feature/deskly-openapi
  3. Review what changed:

    git status -u

    Expect new or modified files under postman/specs/ (and possibly .postman/resources.yaml).

  4. Stage, commit, and push to your fork:

    git add .
    git commit -m "Add Deskly API OpenAPI spec via Native Git"
    git push -u origin HEAD

    Using HEAD pushes 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 from git 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.