Once Pull Request is merged into develop - more features, fixes, chores, refactors etc. MAY be added - it reassembles flow of Git Flow(however, we let our releases to be handled by machines with use of semantic-release). This workflow is compatible with Github Flow - and MAY be used instead(by pushing changes directly to master branch - if so, go directly to point 3)
After all necessary changes are pushed to develop - you MAY decide to use current branch state for release by targeting master - or use next, alpha, beta for better release control.
Merging releasable branch into master will run tests, lint the code(and provide output if necessary), build the documentation and code.
Once merged this time semantic-release will run to create the Github Release, release notes, new entries to CHANGELOG, notify Slack, package and deploy to NPM and Github Package Repo, label the release, and notify any issues of it's deployment.
After semantic-release-bot commits the release commit, this code will be pushed to the release branch under release/0.0.0.