Unify GitHub Actions workflows and add production deployment support #368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR consolidates multiple GitHub Actions workflows into a single unified CI workflow and adds support for deploying to production from the
releasedbranch.Changes
Workflow Consolidation
.github/workflows/main.yml→.github/workflows/ci.ymlverify_components.ymlinto the main CI workflow as a jobdeploy.ymlworkflow (Fly.io deployment)CI Workflow Improvements
releasedbranch to push triggersactions/checkoutfrom v5 to v610.8.0for consistencybin/rails db:test:prepare testverify_componentsjob to ensure component generation is up-to-datenext-deployjob to depend onverify_componentsDeployment Enhancements
released-deployjob that deploys to Heroku production (rubyui.git) when pushing toreleasedbranchnext-deployjob name for clarity (deploys torubyui-next.git)Dependencies
dockerfile-railsgem from Gemfile (no longer needed)