-
Notifications
You must be signed in to change notification settings - Fork 1.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
ci: Compute sha1 from ref in advance in lab and screenshot workflows #6811
ci: Compute sha1 from ref in advance in lab and screenshot workflows #6811
Conversation
Selenium workflow changes verified. |
6c6083d
to
f15a66d
Compare
Incremental code coverage: No instrumented code was changed. |
There is an issue with the update-time check in context of the "Update Screenshots -> Selenium Lab" workflow. Working on that this morning. |
…eenshots to selenium-lab-tests instead of pr number
Updated to pass the computed sha1 from "Update Screenshots" to "Selenium Lab", so we don't have to compute it twice in that nested scenario. To do this well, I'm migrating the "compute ref" step to an external action (which will go up for review as soon as it's tested and working). |
…6811) Always compute sha1 in lab and screenshot workflows in advance. A symbolic ref can change mid-workflow if the repo changes. Co-authored-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
…6811) Always compute sha1 in lab and screenshot workflows in advance. A symbolic ref can change mid-workflow if the repo changes. Co-authored-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
…rkflows (shaka-project#6811)" This reverts commit a472194.
Always compute sha1 in lab and screenshot workflows in advance. A symbolic ref can change mid-workflow if the repo changes.