Open mofojed opened 3 years ago
More detail on a suggested approach: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
Should link to an existing workflow anyway: https://www.atlassian.com/git/tutorials/comparing-workflows
We've got the web version syncing to web, but we still need to detail when/how we update version (whether automatic or manual, should be detailed in the README.md).
Personally I'd love to see a develop/main approach with gitflow, using conventional commits to automatically bump the version on breaking changes.
Define the versioning process used and put in the README.md. An example would be https://semver.org/
Suggest that we simply have a master branch, then we tag it with a release, and create a branch for that with patch versioning if necessary.