-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(travis): remove travis CI, replace with GH Actions #400
Conversation
…5 changes" This reverts commit 88ea5d7.
The style in this PR agrees with This formatting comment was generated automatically by a script in uc-cdis/wool. |
tests/ci_commands_script.sh
Outdated
# since this whole thing is run as a bash {{this script}}, only the last pytest | ||
# command controls the exit code. We actually want to exit early if something fails, | ||
# so check that here and exit as necessary | ||
RESULT=$? | ||
if [ $RESULT -ne 0 ]; then | ||
exit 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it work to just set -e
at the beginning of the script?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done and I tested it works by purposing failing a test in the middle run 👍
setup-script: 'tests/ci_setup.sh' | ||
test-script: 'tests/ci_commands_script.sh' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since these 2 values are the same as the defaults, you could remove them from here, unless you want it to be more explicit where the files are used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I figured since: a) I was gonna use this as an example PR for others to base theirs and b) it's clearer how it's working this way, it'd be better to be explicit
New Features
Breaking Changes
Bug Fixes
Improvements
Dependency updates
Deployment changes