Sorry meaning we have that option so I can merge when it succeeds
On Wed, Dec 17, 2025, 2:55 PM Nicholas DiPiazza <[email protected]> wrote: > Yep as long as we can get merge when succeeds I'm happy camper > > On Wed, Dec 17, 2025, 2:39 PM Tim Allison <[email protected]> wrote: > >> How is it more stable if we allow overrides when ci doesn't work? >> Hudson/Jenkins have been quite flaky, but github has been _pretty good_? >> >> I do like "merge when succeeds". Do we need overrides for that? >> >> >> >I prefer it to be the responsibility of every user to test locally before >> committing. >> Sorry. I've been relying more and more on PRs triggering actions for that. >> certainly not on main. >> >> On Wed, Dec 17, 2025 at 1:17 PM Tilman Hausherr <[email protected]> >> wrote: >> >> > I'm not sure if I like that but I'd love to hear other opinions. The CI >> > build takes very long, and the CI isn't really reliable. And if override >> > can be allowed then it's not really a strong rule. I prefer it to be the >> > responsibility of every user to test locally before committing. >> > Tilman >> > >> > Am 17.12.2025 um 19:09 schrieb Nicholas DiPiazza: >> > > i suggest we make a change to apache/tika github >> > > >> > > main branch requires passing CI >> > > but override can be allowed. >> > > >> > > reason: this allows us to keep main more stable, and also allows us to >> > use >> > > the "merge when succeeds" >> > > >> > >> > >> >
