>> For commits made to git branches that are for restricted upstream branches, such as 'trinity', such a footer *must* be present, and *must* reference an approved upstream ticket, or Gerrit automation shall post a negative vote on the Gerrit review.
This would be an example application, but I guess the footer could be used for integration with any system, theoretically. +1 On Mon, Jun 10, 2024 at 17:16 Ian Maxon <ima...@apache.org> wrote: > +1 > > On Jun 10, 2024 at 13:49:59, Chris Hillery <c...@hillery.land> wrote: > > > For AsterixDB commits which are related to tickets in third-party bug > > tracking systems such as Couchbase Jira, the commit message may include a > > footer such as > > > > Ext-ref: MB-12345 > > > > (A "footer" is a line in a commit message such as the Change-Id: line. > All > > footers must be at the end of the commit message, on separate lines, with > > no intervening blank lines. The set of footers should be offset from the > > main body of the commit message with a blank line.) > > > > The value on the Ext-ref: line should be a simple ticket reference, such > as > > a Jira ticket ID (not a full URL to the ticket). > > > > For commits made to git branches that are for restricted upstream > branches, > > such as 'trinity', such a footer *must* be present, and *must* reference > an > > approved upstream ticket, or Gerrit automation shall post a negative vote > > on the Gerrit review. > > > > For commits made to unrestricted git branches, such a footer *should* be > > included when a third-party ticket is known to be tracking an issue > related > > to the change. > > > > Ceej > > aka Chris Hillery > > >
