- Tag a commit in the repository with the format of
v*.*.*
for production releases, and a tag ofv*.*.*-qa.*
for QA / test releases. For example,v1.6.2-qa.3
. - Push the tag to origin
- The
release.yml
action should create a draft release, with the game'srbxl
file automatically attached to it. - Add a description to the draft release. Typically this will be release notes.
- Publish the release as either a full release or a pre-release.
- The
deploy.yml
action will deploy the place file to either your production environment or your test environment, depending on the naming of the tag. - Your game is now deployed to the proper environment!
Lints will automatically occur when a pull request targeting the master
or v*.*.*
branches is filed, and when a commit is pushed to those branches