-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
tests: clean devtools repo in CI #13758
Conversation
# The only way the folder already exists _and_ there is a cache-miss is | ||
# if actions/cache@v2 `restore-keys` has provided a partial environment for us. | ||
# Do the same as for local, but don't clean! That would toss out all the |
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.
avoiding clean
only makes sense if we were doing -x
. but without that flag git will not touch the ignored folders it knows about, which is where the build artifacts are.
@@ -24,12 +24,11 @@ then | |||
git pull --ff-only -f origin main |
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 know these two branches are the same but I don't care. do you really want to read a compound bash logic if? because I don't want to write one.
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.
Release me from this hell
Fixes the merge issue we were getting in devtools CI build step.
there was an issue with landing a new test file in devtools repo first
https://github.com/GoogleChrome/lighthouse/runs/5591661464?check_suite_focus=true#step:11:52