Very cool, I wonder how GH knows not to merge if any build in the PR failed.
Gary On Fri, Dec 2, 2022, 13:43 Volkan Yazıcı <vol...@yazi.ci> wrote: > Via GitHub Actions: > > https://github.com/apache/logging-log4j-tools/blob/master/.github/workflows/build.yml#L71 > > On Fri, Dec 2, 2022 at 2:17 PM Gary Gregory <garydgreg...@gmail.com> > wrote: > > > That's cool! How is that set up? > > > > Gary > > > > On Fri, Dec 2, 2022 at 8:11 AM Volkan Yazıcı <vol...@yazi.ci> wrote: > > > > > > In the context of LOG4J2-3628 (replacing `maven-changes-plugin`), I am > > > overhauling the `log4j-tools` project. I have done something, if I may > > say, > > > A-W-E-S-O-M-E, which I would like to repeat for Log4j too at some > point: > > > https://github.com/apache/logging-log4j-tools/pull/5 > > > > > > What is exactly happening in this PR? dependabot creates a PR for a > > > dependency update, CI executes the tests, tests succeed, CI merges the > > PR, > > > and publishes the built SNAPSHOT artifact. No more manual dependency > > > updates! > > >
