-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
Prohibited branch detection does not work #245
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
peaceiris
added a commit
that referenced
this issue
May 28, 2020
@peaceiris, thanks for following up. I see my mistake. I think the README is clear now. |
It works well now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When users set a
publish_branch
that is the same as a branch triggered by the workflow, this action stops the deployment to protect the branch.actions-gh-pages/src/set-tokens.ts
Lines 76 to 81 in e3404eb
Currently, this protection behavior does not work.
To Reproduce
With
peaceiris/actions-gh-pages@v3
Expected behavior
This Action should return the error
You deploy from master to master
Screenshots
Your YAML file
Additional context
I found this bug in this article: AsciidocのドキュメントをGitHub Actionsを用いてGitHub Pagesで公開する。 - Qiita
This protection should be also implemented for
personal_token
,deploy_key
, andeventName === 'pull_request'
.The text was updated successfully, but these errors were encountered: