Your progress is only saved in this browser. to protect it and pick up on any device.

Connect a Postman API key to check your work

You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.

0 of 1 steps0%

Your collection now lives as files in the repo. Push them to a feature branch on your fork — that's all LiftOff needs. You do not need to open a pull request, merge anything, or contribute back to the source repo.

1

Push with the Postman Terminal

Commit and push from the Postman terminal — same one you used to run the server. Use a feature branch (not main) so your API changes sit in version control the way a real team would work.

  1. Stop the Deskly server if it's still running: Ctrl+C in its terminal.

  2. Create and switch to a feature branch (watch the branch name update bottom-left):

    git checkout -b feature/deskly-collection
  3. See what Native Git wrote:

    git status -u

    Expect .postman/resources.yaml and files under postman/collections/.

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

    git add .
    git commit -m "Add Deskly API collection via Native Git"
    git push -u origin feature/deskly-collection

That's enough for this module. LiftOff checks that your collection files exist on a feature/ branch in your fork — no PR required.

Optional — preview the diff on GitHub: After pushing, GitHub may show a Compare & pull request link. You can click it to see your YAML files as a reviewable diff, then close the page. You don't need to submit or merge the PR — especially not against the original Postman-Devrel/deskly-api repo.

Troubleshooting

  • git status shows nothing — recheck Part 1 Step 3 (folder connected in Local View).
  • .postman missing — check .gitignore isn't excluding dot-directories; resources.yaml must be committed.