Skip to content
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

Support @quarkusbot retest command #71

Open
gastaldi opened this issue Apr 13, 2021 · 4 comments
Open

Support @quarkusbot retest command #71

gastaldi opened this issue Apr 13, 2021 · 4 comments

Comments

@gastaldi
Copy link
Contributor

It would be nice if we could retrigger the build by commenting something like @quarkusbot retest. Eg. In PRs which updates a dependency that is not in Central yet

This would be useful in conjunction with #23

@gastaldi gastaldi changed the title Support retest command Support @quarkusbot retest command Apr 13, 2021
@glefloch
Copy link
Member

I was looking at this one but I can't find a simple way to react to mentions. I'm not even sure we can mention an app. I don't know how dependabot works.. @gsmet have you some hints?

@gsmet
Copy link
Member

gsmet commented Apr 26, 2021

I think you will have to listen to IssueComment. Note that it's a bit of a pain because you have to check if it's a PR (you have a method for that) and then get the associated pull request and from there you should be able to make progress.

I would do something with a pattern such as ^@(?:quarkus-?)?bot\s+([a-z _\-]+)\s+ and make it case insensitive.

And then have a map of commands.

I would also ignore the comments added by the bot itself but we can add that later as you will need the ability to inject GHMyself and I haven't worked on this yet.

@gsmet
Copy link
Member

gsmet commented Apr 26, 2021

Ah and better check the pattern before getting the pull request itself, that will avoid one API call.

@glefloch
Copy link
Member

Thanks I was missing the part on pull request comment which are issue comments. I will go your way :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants