I hope there is an author of the post. I appreciate sharing this example.

However, there is a caveat regarding the workflow code itself, that placing "run" statement with specific commands directly in YAML may make it difficult to debug locally. I would recommend that "run" statements be only for script execution and their number minimized. This way, scripts can be run locally without waiting for the entire CI pipeline to execute each time.

This doesn't really say much about publishing games from GitHub Actions. There's about 3 lines that reference https://github.com/game-ci/steam-deploy which contains the actual implementation.

How do you deal with Steam Guard code?

Why? For most games (especially a "2d hide and seek") you drop a zip file and press a single button on your dev console to publish.

Congratulations! Nice job man.

undefined

What's the idea here, to make it easier for lazy devs to push builds to paying customers without even stopping to play test it themselves first? Streamlined publishing makes negligence easier and more enticing.