DEV Automated Release System

What?

This is how we can make releases to the development test server, and the Steam Workshop, from GitHub itself.

How?

Using GitHub Actions triggered by normal GitHub events.

Deploying to the Development Server

To do this just accept a PR to the development branch (or commit to it, but you should prefer PRs). The GitHub action Build Dev will run automatically, making a new build and pushing the mission pbos to the Development Server.

Deploying to Steam Workshop

To do this you should use Pull Requests to merge your changes from development to master branch. Click here to start a new one.

This will trigger the Release Drafter GitHub action, creating or updating a draft release.

Once you are happy with the changes in master you should review the draft release, confirming the version number and changelog are appropriate. You can edit these freely. The version number should have been automatically incremented to have a minor version 1 greater than the previous release. This is normally correct; only very occasionally will we increase the major version number.

When you are happy with the changelog and version number you should publish the release (marking it prerelease if we are still in alpha).
This will trigger the Publish to Workshop GitHub action automatically, publishing to Steam Workshop using the latest version in master and the changelog from the release. It will also attach the latest build to the release itself.

That's it!