The NeplodeAPI uses a Dev-Staging-Prod branching flow.
The dev branch is where all in-development commits go. If you just finished a new system but haven't done full bug-checking or something along those lines. It goes to dev. Local work should always be committed to dev, until it's reviewed by a peer.
Once the code is complete and checked to be free of any API-Breaking bugs, it is committed to staging. Staging is where all complete features or commits are stored.
When we are ready to release an update, all commits from staging are committed to prod, which is then deployed to the API on our server.