search

ubiquity / ubiquibot

Putting the 'A' in 'DAO'
https://github.com/marketplace/ubiquibot
MIT License
17 stars 59 forks source link

Pull Request Review: Automated Follow Ups #254

Open 0x4007 opened 1 year ago

0x4007 commented 1 year ago

Similar to how the bot follows up with bounty hunters if there is no activity in a few days, it would be lovely if the bot can follow up with requestors and requestees of pull request reviews.

For example, a bounty hunter opens up a pull request and I request a review from 0xcodercrane. In 3-4 days (we can use the exact same logic as bounty hunter follow ups) the bot should comment in the pull request asking:

"@ 0xcodercrane @ pavlovcik are there any updates?"

seprintour commented 1 year ago

The usernames will be subject to change right?, so it'd be stored in a global object

ubiquibot[bot] commented 1 year ago

Available commands

- /assign: Assign the origin sender to the issue automatically.
- /unassign: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /payout: Disable automatic payment for the issue.
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address. 
  ex1: /wallet 0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266 
  ex2: /wallet vitalik.eth

@seprintour

seprintour commented 1 year ago

Okay

0x4007 commented 1 year ago

I don't understand your question. User names should be dynamically read from the GitHub pull request. They should not be stored in an object unless you're referring to that instance's runtime memory.

seprintour commented 1 year ago

I don't understand your question. User names should be dynamically read from the GitHub pull request. They should not be stored in an object unless you're referring to that instance's runtime memory.

I was referring to the usernames that should be tagged for review

0x4007 commented 1 year ago

I don't understand but if you open a pull request we can give you feedback.