Re: git: 6c93a2d0bc37 - main - [skip ci] improvements to cap_sysctl.3

From: Cy Schubert <Cy.Schubert_at_cschubert.com>
Date: Thu, 08 Dec 2022 23:06:20 UTC
In message <20221208232454.32fbd074896a1834cd7b2737@bidouilliste.com>, 
Emmanuel
 Vadot writes:
> On Thu, 8 Dec 2022 15:15:30 -0700
> Alan Somers <asomers@freebsd.org> wrote:
>
> > On Thu, Dec 8, 2022 at 2:59 PM Emmanuel Vadot <manu@bidouilliste.com> wrote
> :
> > >
> > > On Thu, 8 Dec 2022 14:28:34 -0700
> > > Alan Somers <asomers@freebsd.org> wrote:
> > >
> > > > On Thu, Dec 8, 2022 at 2:15 PM Emmanuel Vadot <manu@bidouilliste.com> w
> rote:
> > > > >
> > > > >
> > > > >  Hi Alan,
> > > > >
> > > > > On Thu, 8 Dec 2022 19:46:01 GMT
> > > > > Alan Somers <asomers@FreeBSD.org> wrote:
> > > > >
> > > > > > The branch main has been updated by asomers:
> > > > > >
> > > > > > URL: https://cgit.FreeBSD.org/src/commit/?id=6c93a2d0bc37f0c912e402
> f3f94c3c01350dca26
> > > > > >
> > > > > > commit 6c93a2d0bc37f0c912e402f3f94c3c01350dca26
> > > > > > Author:     Alan Somers <asomers@FreeBSD.org>
> > > > > > AuthorDate: 2022-12-01 16:49:57 +0000
> > > > > > Commit:     Alan Somers <asomers@FreeBSD.org>
> > > > > > CommitDate: 2022-12-08 19:45:47 +0000
> > > > > >
> > > > > >     [skip ci] improvements to cap_sysctl.3
> > > > >
> > > > >  You keep doing commit with this [skip ci] prefix, what is it for ?
> > > > >  AFAIK the official FreeBSD CI doesn't support this and I find that
> > > > > really ugly to have this in the commit subject.
> > > > >  Mind sharing more on why you add this ?
> > > > >
> > > > >  Cheers,
> > > > >
> > > > > --
> > > > > Emmanuel Vadot <manu@bidouilliste.com> <manu@FreeBSD.org>
> > > >
> > > > It tells CI systems not to run any tests on this commit.  Both Cirrus
> > > > and Jenkins understand it, among others.  For example, if you browse
> > > > to https://github.com/freebsd/freebsd-src/commits/main and hover over
> > > > the green checkmark next to this commit, you'll see a bunch of
> > > > "skipped" symbols.  So I use it just to save resources.  I think I
> > > > could put it on a separate line, though.
> > > > -Alan
> > >
> > >  Mhm ok, I find that very ugly, couldn't we add some git push options
> > > instead ? We use gitlab at current work and we use a lot of those push
> > > options, this avoid having ugly commit subject.
> > 
> > 
> > How?  What is a "git push option"?
>
> https://docs.gitlab.com/ee/user/project/push_options.html
>
>  This is the same kind of stuff we use when you push some commit
> authored by someone without a @freebsd.org email address.

Seems Github and Gitlab accomplish the same thing, differently.

https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-
runs

But our CI happens in jenkins. Wouldn't push options and "magic" strings in 
commit logs mean nothing in our case, because we use cgit and jenkins?

I don't understand how skipping Github workflows does anything to affect 
our jenkins workflow.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  https://FreeBSD.org
NTP:           <cy@nwtime.org>    Web:  https://nwtime.org

			e^(i*pi)+1=0