-
Notifications
You must be signed in to change notification settings - Fork 784
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 skip-ci on stable
#5909
Fix skip-ci on stable
#5909
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.
As much as I hate "null"
as a string, this looks like it would work
LGTM
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
@Mergifyio requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 1bcd1f1 |
Issue Addressed
Fix
skip-ci
job triggered by pushing to branches. Also replaced the deprecated::set-output
command.I've tested this on a push to my fork, and it evaluates
null
without failing:https://github.com/jimmygchen/lighthouse/actions/runs/9457252549/job/26050717847