-
Notifications
You must be signed in to change notification settings - Fork 60
Rouge /help
Command Output
#244
Comments
/start |
@0xcodercrane The time limit for this bounty is on Wed, 12 Apr 2023 01:05:17 GMT |
/wallet 0x00868BB3BA2B36316c2fc42E4aFB6D4246b77E46 |
Updated the wallet address for @0xcodercrane successfully! Your new address: |
/help |
Available commands
|
@pavlovcik ^^ |
Please review the referenced conversation. The bot seems to think that devpanther is a first time contributor and posted the tutorial help message output. The reason why I'm confused and am asking for a diagnosis is because he had nothing to do with that issue that the bot tagged him in. |
/wallet 0x00868BB3BA2B36316c2fc42E4aFB6D4246b77E46 |
Updated the wallet address for @0xcodercrane successfully! Your new address: |
taking a look |
@pavlovcik you merged the above PR but sorry for not jumping on the review |
Regarding the review: it was difficult the previous couple weeks having to review from phone. I wish it indicated it was reviewed on GitHub mobile and to take it with a grain of salt.
This doesn't answer why devpanther was tagged in an unrelated issue. |
Do you have any updates @0xcodercrane? If you would like to release the bounty back to the DevPool, please comment |
I understand your concern. lets ask to @devpanther about that. |
Do you have any updates @0xcodercrane? If you would like to release the bounty back to the DevPool, please comment |
I am just waiting for @devpanther 's reply |
Um, don't really know what this issue is about.. At the time it happened, I know I was looking around the repos but don't remember commenting on that issue |
But I think something triggered it |
Releasing the bounty back to dev pool because the allocated duration already ended! |
1 similar comment
Releasing the bounty back to dev pool because the allocated duration already ended! |
It seems like an inexplicable glitch for why the bot decided to tag devpanther with the help menu on an unrelated issue. Please diagnose and fix this problem.
@devpanther
Originally posted by @ubiquibot[bot] in ubiquity/pay.ubq.fi#19 (comment)
The text was updated successfully, but these errors were encountered: