The branch for this issue is release-notes-16-1 and GitLens thinks these two issues (#16 and #1) are associated but they are not. I suspect the matching algorithm needs to be refined to avoid mismatches like this.