-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Two PRs are created instead of one: the first one is incorrect, the second one is as expected #656
Comments
@sglavoie Thanks for reporting this one. Looks like the issue lies within the comment you made which is a complex one.
I will check this one later. |
@all-contributors please add @sglavoie for bug |
I've put up a pull request to add @sglavoie! 🎉 |
Thank you @tenshiAMD! If that helps, here are a couple more cases where I wrote what might be considered a complex comment including a command for all-contributors (those all worked, two of them included an emoji too): |
@sglavoie These are valid examples however I found the issue here
since you used the pronoun |
Describe the bug
Two PRs are created instead of one. The first one is irrelevant (wrong username and wrong emoji key) while the second one (which got created after manually closing the first one) gets created correctly.
To Reproduce
Steps to reproduce the behavior: it is unclear how this can be reproduced, but here's a link to the issue where the bug happened.
@all-contributors please add @<username> for bug
Expected behavior
A single PR should be created, i.e. this one.
Screenshots
Here, it can be seen that two PRs were created.
Additional context
Here's what happened for the above screenshot to have gotten to where it is (timezone in
CDT
):@all-contributors please add @<username> for bug
is invoked from a comment inside an issue.Please make sure to use valid contribution names
, however the original request was for the emojibug
, which is listed in the Emoji Key table.We have benefited tremendously from all-contributors so far in the above linked repo! Thank you very much! 🙂
The text was updated successfully, but these errors were encountered: