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.
This PR sets up GitHub Actions for the CMS backend. In the process, we also remove our Travis configuration file since we don't want to double build and subsequently deploy simultaneously to elastic beanstalk. One thing to note with this change is that we will not be able to specify the S3 bucket name to which our package will be deployed. However, since this isn't a huge downside + Travis is no longer free for open-source, we will be sticking to GitHub actions.
These changes were tested with the
DEV_BRANCH
set to this branch (refs/heads/setup-github-actions
). Refer to theActions
tab on this repo for example workflows run.