-
Notifications
You must be signed in to change notification settings - Fork 2
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
Github Workflow refactor #297
Conversation
…ts. Deleted upload-artifacts workflow
…rtejoso/refactor-workflows
…rtejoso/refactor-workflows
…-io/contracts into jcortejoso/refactor-workflows
.github/workflows/release-github.yml
Outdated
- name: Compile and Lint | ||
run: | | ||
yarn lint | ||
yarn clean | ||
sh ./scripts/build.sh | ||
yarn compile | ||
|
||
- name: Run Unit Tests | ||
run: | | ||
yarn test:unit | ||
|
||
- name: Run Integration Tests | ||
run: | | ||
yarn test:integration |
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.
does it make sense to lint and test before releasing? Typically you do a release on a green branch or you may want to do an rc
release in a broken branch
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.
Happy to remove. I copied the building process to generate the artifacts, but I agree validating the release should not be needed as we should not release/merge when that is not green in any case.
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.
Updated
Description
upload-artifacts.yml
workflow (this atm must be executed locally by the contract deployer).Is this PR related with an open issue?
Related to Issue #
Types of changes
Checklist:
Funny gif