-
Notifications
You must be signed in to change notification settings - Fork 8
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
CLA bot seems to be running against issue comments #10
Labels
bug
Something isn't working
Comments
Gudahtt
added a commit
to Gudahtt/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to Gudahtt/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to Gudahtt/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to MetaMask/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to Gudahtt/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to MetaMask/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to Gudahtt/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to MetaMask/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
Gudahtt
added a commit
to Gudahtt/cla-signature-bot
that referenced
this issue
Aug 26, 2020
The bot is currently triggered for comments on both issues and pull requests, but the bot has no purpose on issues. If the job does end up getting run, it will fail with an error. The example in the README has been updated to skip the job when triggered by issue comments. The runner will also bail early if it determines that it's being run for an issue comment rather than a pull request comment, instead of blowing up when it tries to get the pull request authors. Fixes Roblox#10
I believe you need to remove the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After making a comment on an issue on a repo with the CLA bot, it sent me an email that it had failed.
https://github.com/Roblox/testez/actions/runs/172094273
This did not stop me from commenting BTW.
Expected behavior
The CLA bot probably shouldn't run at all for issues and issue comments.
The text was updated successfully, but these errors were encountered: