jPOS-template adopts Tip and Tail
· 2 min read
In our Tip‑and‑Tail announcement we described the new branch model we’re rolling out across the jPOS ecosystem. The jpos/jPOS-template repository now follows that scheme:
| Old branch | New branch | Purpose |
|---|---|---|
next | main | tip branch (default) |
next-multimodule | main-multimodule | tip branch for the multimodule tree |
master | tail | trails the latest tagged release |
multimodule | tail-multimodule | tail branch for the multimodule tree |
If you already have the template checked out, you only need to teach Git the new names—no history was rewritten.
Updating an existing clone
git fetch origin --prune
git branch -m next main
git branch -u origin/main main
git branch -m next-multimodule main-multimodule
git branch -u origin/main-multimodule main-multimodule
git branch -m master tail
git branch -u origin/tail tail
git branch -m multimodule tail-multimodule
git branch -u origin/tail-multimodule tail-multimodule
That’s it—your local branch names now match the remote.
Need the quickest path?
Grabbing a fresh copy of the repo is always the simplest option:
git clone https://github.com/jpos/jPOS-template.git
cd jPOS-template
GitHub serves main by default. If you’re working with the multimodule example, switch to main-multimodule:
git switch main-multimodule
From here on out, whenever our docs mention “tip” think main (or main-multimodule), and whenever they mention “tail” think tail (or tail-multimodule). Happy hacking!