On Wed, 2023-02-01 at 17:53 -0800, Paul E. McKenney wrote: > On Thu, Feb 02, 2023 at 10:49:15AM +0900, Akira Yokosawa wrote: > > Hi, > > > > On Wed, 1 Feb 2023 14:13:02 -0800, Paul E. McKenney wrote: > > > On Wed, Feb 01, 2023 at 05:15:29PM -0300, Leonardo Bras wrote: > > > > Having this file merged on the main repository will trigger the Gitlab-CI > > > > on the mirror: https://gitlab.com/linux-kernel/perfbook/ after each push. > > > > > > > > The way it works: > > > > - Compile-test CodeSamples > > > > - IF pass, build PDFs: regular, 1c, eb > > > > > > > > Signed-off-by: Leonardo Bras <leobras.c@xxxxxxxxx> > > > > > > Queued and pushed, thank you! Let's see how github (as oppoed to your > > > gitlab) reacts to this. ;-) > > > > I happen to have a perfbook repo at gitlab where CI is not set up. > > When I pushed this change, I got a mail from gitlab saying: > > > > > Subject: perfbook | Failed pipeline for gitlab-ci | 55c81b9b > > > > > > Pipeline #764856510 has failed! That's odd, I wonder why have it failed. > > > > I don't think it is reasonable for Paul's repo to have gitlab > > specific settings like this. > > > > Paul, can you please revert this? > > Done, and apologies! > > Leonardo, would another approach be to create a separate branch in your > repo that contained this file, then automatically cherry-pick or merge it > with each perfbook update? > > Thanx, Paul Sure, that would work much better, but I need to find out how to do this on Gitlab side. I will reply here when I find any answers. Thanks!
