Add automated itch.io deployment workflow for master and tags #4
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Status: Draft
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
floride/bevy_template#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Set up an automated CI pipeline (Forgejo Actions runner) to build and deploy our Bevy game to Itch.io. The workflow should target two deployment streams: automated development builds from the
masterbranch, and stable production releases when a version tag (v*) is pushed.Technical Details
Create a workflow file.
Triggers:
Push to
masterbranch (deploys to itch.io channel:dev).Push to tags matching
v*(deploys to itch.io channel:stable).Jobs required:
Install system dependencies for Bevy compilation (e.g.,
alsa,udevon Linux runners).Build target binaries (e.g., WASM/Web and/or Native Desktop).
Utilize the Itch.io
butlerCLI tool (via a pre-built action or binary download) to push the build artifacts.Secrets needed:
BUTLER_API_KEYmust be configured in the repository settings.Acceptance Criteria
master.v1.0.0is pushed.