-
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
Fix regex in getStagingDeployCashInternalQA #9523
Conversation
[...internalQASection.matchAll(new RegExp(`- \\[([ x])]\\s(${ISSUE_OR_PULL_REQUEST_REGEX.source})`, 'g'))], | ||
[...internalQASection.matchAll(new RegExp(`- \\[([ x])]\\s(${PULL_REQUEST_REGEX.source})`, 'g'))], |
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.
For this one specifically, shouldn't we keep ISSUE_OR_PULL_REQUEST_REGEX
?
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.
Oh no nevermind, it's only used in getStagingDeployCashPRList
where we only care about PRs.
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.
Going to approve and merge as discussed on Slack, some PRs are failing until then.
This fixed the workflow but it appears that the internalQA checkbox lost it's state? cc @mountiny |
🚀 Deployed to staging by @francoisl in version: 1.1.78-5 🚀
|
Ahhh, some bad copypasta! Thanks for the quick fix Rory! |
🚀 Deployed to production by @sketchydroide in version: 1.1.78-8 🚀
|
Details
This just fixes the regex in
getStagingDeployCashInternalQA
so that it doesn't pick up deploy blockers beneath. Tested with https://regexr.com/Fixed Issues
$ #9500
Tests
QA Steps
preDeploy.yml
workflow should succeed.