You'll commit and push right from the same Postman terminal you used to run the server, so there's no need to leave the app. You'll put the change on a feature branch rather than straight to main — the way you'd version a real API change — and since Postman follows your current Git branch, you'll see the branch name update in the bottom left. Pushing sends the collection files (and the .postman/resources.yaml map Native Git created on connection) up to your fork.

1. Stop the Deskly server if it's still running: focus its terminal and press Ctrl+C — you're now back at a prompt in the same Postman terminal.

2. Confirm you're in the connected deskly-api folder, then create and switch to a feature branch. Watch the branch name update in the bottom left of Postman:

   Copy

   git checkout -b feature/deskly-collection

3. Review what Native Git wrote, using -u to list every untracked file:

   Copy

   git status -u

   You should see a .postman/ directory (holding resources.yaml) and a postman/ directory with your collection.

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

   Copy

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

5. Now open the pull request — the payoff of Native Git. Fastest route: right after the push, GitHub prints a "Create a pull request" link in the terminal output — Cmd+click (Ctrl+click on Windows/Linux) it to open the PR straight in your browser. Otherwise, on GitHub your freshly pushed branch shows a Compare & pull request banner; click it (or go to Pull requests → New pull request and set feature/deskly-collection as the compare branch). Scroll down to Files changed and you'll see your work as a reviewable diff: .postman/resources.yaml plus each request under postman/collections/Deskly API/ as its own YAML file. That's the whole point of Native Git — an API change reviewed exactly like code, in a single pull request. You don't need to merge it: this is your personal fork, so opening the PR to view the diff is enough (close it afterwards if you like).

Troubleshooting: If git status -u shows nothing to commit, the folder may not be connected — recheck Part 1 Step 3. If .postman is missing from the diff, make sure your .gitignore isn't excluding dot-directories; that file must be committed.