Hey @sortanderw,
We follow a standard of WIP/feature branch -> dev -> test -> production.
The dev, test, and production branches are all locked down and require a Pull Request and Approval from a teammate.
The WIP branch, or work-in-progress branch is generally developer specific and relates to a Jira story, incident, or other ticket number. When sandboxes are available for us to use this would ideally be what developers are using to develop and push into the sandbox instance. When ready, they would merge and deal with any conflicts within the Pull Request from the WIP branch to the dev branch.
We do utilize a CI/CD tool to migrate the code from branch to branch after the initial PR into the dev branch.
The actual version of the application does get a little tricky because that is defined when you publish the application from the instance into ServiceNow's repo (which last I checked was recommended for deploying to production). Currently, you can update the 'version' of the app in the package.json, but it doesn't really mean anything to us at the moment because that version is not related to what is published into ServiceNow's repo.
What we have done in the interim is to utilize our CI/CD job id to determine the version of the app that gets deployed into production.
I don't feel like we are all the way there from a maturity standpoint, but we have made gains to develop and migrate code in a more standardized way (with most of the diversion from the standard happening when trying to go to PROD due to how the application gets published from the instance rather than from the SDK).
Hope this helps you on your path!
Brady Holliday
