These tickets have all met the standard integration requirements, so I’m
> just unclear what “higher pre-commit gateway” you are referring to.
>


A merge into trunk deserves extra eyeballs than a merge into a feature
branch.

We can refer to this as a "higher pre-commit gateway" or a "second pass".
Either way I believe it is a good thing.



> I think the existing epics are probably more natural tickets to reference
> in the merge, eg 17091 and 17092.
>


If _all_ tickets in that epic are being merged, sure. Otherwise how can I
see what resolved tickets are in trunk and what resolved tickets are not…

I would rather not have to be working on accord actively to be able to see
this stuff quickly.

Reply via email to