-
Notifications
You must be signed in to change notification settings - Fork 208
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
ci(restore-node): detect staged yarn.lock, package.json #8168
Conversation
cea5cb9
to
70cb214
Compare
# (First column is non-space, second column is space, followed by separator.) | ||
if [ -n "$(git status --porcelain | grep -Eve '^[^ ] '; true)" ]; then |
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.
I think '^M '
would work too, right?
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.
Yes, that should work too. Would you prefer it?
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.
It'd be a little clearer, but I don't care enough to request a change
ci(restore-node): detect staged yarn.lock, package.json
ci(restore-node): detect staged yarn.lock, package.json
ci(restore-node): detect staged yarn.lock, package.json
#not-endo-branch: master
refs: #8155
Description
I didn't correctly test #8155 against an Endo branch, so it failed during the nightly scheduled job. Let's try again:
yarn.lock
andpackage.json
when setting#endo-branch: XXX
notify-status
action from the correct path fortest-dapp-*.yml
Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
n/a
Testing Considerations
Tested CI against Endo master, with one expected failure due to typing changes in the new Endo.
Upgrade Considerations
n/a