I'm a new user of All Contributors, and I'm interested in using it to acknowledge future contributors for an open source toolkit to help develop experimental medical imaging techniques. However, when I installed the GitHub bot app and tried to test it out, the bot returned that dreaded error message:
We had trouble processing your request. Please try again later.
I understand that this is a vague issue that has resurfaced in various forms in the past. I found and tried many of those attempts, but none of these fixes worked for me:
I'm aware that, per this issue, using the CLI seems like the best solution here. However, I'm not really experienced in JavaScript, so I'd like to avoid having to deal with that unless it's truly impossible without it. Given this, could you help me figure out why this is the case and/or what I could do about it?
Note that this is a copy of this issue, which I think I originally put in the wrong repo. If you end up seeing both, please reply to this Issue instead.
To Reproduce
Open an issue or pull request ticket in my repository
Type a comment that should be a valid All Contributors bot request (e.g. @_all-contributors please add @_keitaay for code, but omit the underscores)
Submit that comment
Expected behavior
The requested addition/modification to the contributor's table is added
OR
A specific error is raised by the bot that indicates what needs to be fixed
Describe the bug
I'm a new user of All Contributors, and I'm interested in using it to acknowledge future contributors for an open source toolkit to help develop experimental medical imaging techniques. However, when I installed the GitHub bot app and tried to test it out, the bot returned that dreaded error message:
This has occurred when I tried to call the bot from a pull request as well as in an issues report.
I understand that this is a vague issue that has resurfaced in various forms in the past. I found and tried many of those attempts, but none of these fixes worked for me:
I'm aware that, per this issue, using the CLI seems like the best solution here. However, I'm not really experienced in JavaScript, so I'd like to avoid having to deal with that unless it's truly impossible without it. Given this, could you help me figure out why this is the case and/or what I could do about it?
Note that this is a copy of this issue, which I think I originally put in the wrong repo. If you end up seeing both, please reply to this Issue instead.
To Reproduce
@_all-contributors please add @_keitaay for code, but omit the underscores)Expected behavior