Please use .. comparisons for “Compare Source”

[mtrmac]

Tell us more.

containers/image#2812 was filed by Renovate, with the “Compare Source” link going to mattn/go-sqlite3@v1.14.24...v1.14.25 (three dots). This only shows changes in new commits, and is in fact not representative of the effect of updating in this case, where 1.14.25 was tagged of a branch which does not include all of 1.14.24. (That’s certainly a mistake, but such things can happen.)

A more relevant comparison is https://github.com/mattn/go-sqlite3/compare/v1.14.24..v1.14.25 (two dots), which shows that this release, in effect, triggered a downgrade of an included codebase.

Please consider using double-dot, not triple-dot, comparison links in the PRs Renovate files. Thanks!

[rarkins]

Did you find any documentation (from github) for this difference in behavior between 2 and 3 dots?

[mtrmac]

Sure, that is linked from every GitHub diff page: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests#three-dot-and-two-dot-git-diff-comparisons .

[rarkins]

Those descriptions are referring to branches, whereas 99%+ of the time Renovate's links refer to tags. Is there any difference between .. and ... results when it's tags? I don't think the "most recent version of the topic branch" applies when it's a tag not a branch.

[mtrmac]

I have provided example links in the initial post. See for yourself.