-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[NO QA]Run tests and lint on merge into main #7632
Conversation
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.
LGTM, but Rory knows the actions way better. Leaving it over to you.
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.
Is your intention to prevent preDeploy from triggering a staging deploy if tests fail? If so, I think you need to make other jobs, particularly version
, dependent upon the results of the confirmPassingBuilds
job using the needs
keyword and the job-level if
clause for the version
job.
Got it - I thought that we could just rely on that one job failing to fail the workflow, but I will make that explicit change 👍 |
Ok so I think the latest changes will do what we want? Basically if lint or tests do not pass, don't continue the deploy workflow? |
🚀 Deployed to staging by @roryabraham in version: 1.1.39-0 🚀
|
Details
Runs both the lint and test workflows when we merge code into
main
, which will hopefully prevent us from trying to deploy unlinted code that will cause the builds to fail.Fixed Issues
$ #7026
Tests
QA Steps
N/A
Tested On
N/A