-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Keep alive step failed if the branch is protected #25
Comments
Just got notified that "ddev-browser" stable test failed; seems to be this. |
|
The keep alive action has been fixed with a new 1.2.2 release. Default value of the new Thus, it should work again (worked for me) and we don't have to change anything. |
Confirmed. ddev-browsersync now working. Thank you. |
Since the
1.2.0
release of thegautamkrishnar/keepalive-workflow
, the "keep alive" step failed if the branch is protected (which is a common practice, I guess), even if we set thepermission: write
directive.I opened an issue for this: gautamkrishnar/keepalive-workflow#20
As a workaround, I think we could always pass the new
auto_write_check
tofalse
.The text was updated successfully, but these errors were encountered: