Yeah, I'm looking at here, assuming it's ahead of last release.

You could maybe leave the element off unless it is a larger change. I think my concern here is seeing it on every revision becomes something extra I have to mentally process, but if the intent is to either help show small changes, or large changes, it could just be visible in those edge cases. In those cases at least, the element provides context as to why it's shown at all vs. all the time?

I feel your instincts are correct, this information isn't useful in a list form and shouldn't be included. You could make the argument to include it in a hovercard, or bring it into the header on the diff page, and I think those are both fine. Outside of that this seems mostly geared towards avoiding code review, a practice I don't think is well aligned with the overall product goals.

seems ok

I can also copy-pasta if this is something needed for each application.

So for Ferret is there anything day to day we need to know, or is everything automatic in modern code?

• verify rebase

• rebase #2

rebase