Switch from Travis CI to GitHub Actions (#27) (#29) #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Try installing a few deps * Install Node, Ruby, and attach a Postgres instance * Match the installed version of ruby with the one in ruby-version * Use a clever method for finding the current ruby version actions/setup-ruby#31 (comment) * Oops, gotta checkout the code before reading the version * Bump to the latest patch version of Ruby * Bump the Gemfile too * Health check the Postgres instance and split out the bundle step * use the latest Postgres, reformat the heallth check * Point Rails at the service container * Switch back to port mapping postgres to the local machine * Manually set up the postgres instance and use DATABASE_URL for telling Rails where to look * Deploy using GitHub workflows * Use secrets store * Setup both api. and git. for Heroku * Specify the Heroku app to deploy to * Double check current config * debug heroku auth * Work that netrc * try and preserve newlines when writing netrc * Be extra specific with the GH branch we want to push * Only deploy on master * I read the docs * Install specific node versions * Cache Node Modules runs * Cache Ruby dependencies * Ditch Travis Switch the build badge from Travis to GH Actions ayy wow Clobber the remote ref Fix a Gemfile Ruby version issue Fetch the whole repository because Heroku wants it Keep the Heroku app names secret and Deploy to Production
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Try installing a few deps
Install Node, Ruby, and attach a Postgres instance
Match the installed version of ruby with the one in ruby-version
Use a clever method for finding the current ruby version
actions/setup-ruby#31 (comment)
Oops, gotta checkout the code before reading the version
Bump to the latest patch version of Ruby
Bump the Gemfile too
Health check the Postgres instance and split out the bundle step
use the latest Postgres, reformat the heallth check
Point Rails at the service container
Switch back to port mapping postgres to the local machine
Manually set up the postgres instance and use DATABASE_URL for telling Rails where to look
Deploy using GitHub workflows
Use secrets store
Setup both api. and git. for Heroku
Specify the Heroku app to deploy to
Double check current config
debug heroku auth
Work that netrc
try and preserve newlines when writing netrc
Be extra specific with the GH branch we want to push
Only deploy on master
I read the docs
Install specific node versions
Cache Node Modules runs
Cache Ruby dependencies
Ditch Travis
Switch the build badge from Travis to GH Actions
ayy
wow
Clobber the remote ref
Fix a Gemfile Ruby version issue
Fetch the whole repository because Heroku wants it
Keep the Heroku app names secret and Deploy to Production