Hi Martin,

Overall I think this is interesting for sure. I've got some other comments/questions inline.

On Fri, Jul 21, 2023 at 2:34 AM Martin Stefanko <mstefank@redhat.com> wrote:

Hi,

we created a custom wildfly-github-bot that is ready to be deployed to wildfly/wildfly repository when we get the green light - https://github.com/xstefank/wildfly-github-bot.

It is a Java application that listens for GitHub events and interacts with GitHub's public API.

Is there a reason to have it listen instead of being invoked by a GitHub Action? This allows it to not be hosted on a separate container. By having it an action too it's up to the project whether they want to require the action to be successful or not before merging.

For now, it contains two main features:

1/ PR format verification

Verifies the PR is in the expected format (WFLY-XYZ Test). A simple video showing this in action https://www.youtube.com/watch?v=RgD7RhEegdc.

2/ Automatic /cc comment based on the changed files in the PR:

Instead of a CC could we have it assign the component lead as a reviewer?

For instance, in https://github.com/xstefank/wildfly/pull/65 or https://github.com/xstefank/wildfly/pull/64 you can see that I'm mentioned because the commit changed a file under microprofile/lra subdirectory.

The configuration lives in the project that is utilizing the bot - https://github.com/xstefank/wildfly/blob/main/.github/wildfly-bot.yml. As you can see, mostly everything is configurable.

The bot is currently deployed in the custom OSD (OpenShift Dedicated) cluster that we got provisioned just for this purpose. I would be the main maintainer plus a few guys from SET backing me.

The deployed bot is configured for the https://github.com/xstefank/wildfly repository. Feel free to open as many PRs as you'd like to experiment with the bot. Check the configuration file to see what you can do - https://github.com/xstefank/wildfly/blob/main/.github/wildfly-bot.yml.

Of course, this is just a start. We can add automatic labels, CI triggers, review requests (if wanted), or milestones, etc. We are only limited by what can be done on GitHub.

Thanks,
Martin Stefanko

Principal Software Engineer
Middleware Runtimes Sustaining Engineering Team
Red Hat
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/MM5K33E4DP36H4GGZPMWMW7HTZMFAFQM/

James R. Perkins

JBoss by Red Hat