docs-issue-generation: docs issues are not being created for commits with multiple release notes

[jlinder]

Describe the problem

The docs-issue-generation program does not create docs issues for a commit with multiple release notes:

• ui: make Metrics and SQL timepicker align #83107 is part of this merge commit. It did not have a docs issue created for it. This is the TeamCity run for that merge commit.
• release-22.1: ui: make Metrics and SQL timepicker align #83507 is the backport for ui: make Metrics and SQL timepicker align #83107. It did not have a docs issue created for it. It's merge commit and it's TeamCity run.

The logs for the TC runs that didn't create docs issues have no information about what it found.

Expected behavior

Docs issues should have been created for #83107 and #83507.

Additional context

It'd be great if the program could output some information about what it did to verify it's working as expected.

Jira issue: CRDB-17658

Epic DEVINF-261

[nickvigilante]

@jlinder cockroachdb/docs#14376 was the docs ticket created for #83423. It was just closed shortly after opening by Stephanie. No issue there.

For #83507, there are two release notes within the commit message. Is that allowed practice to include 2 release notes in the same PR? My intuition tells me no.

[jlinder]

Hey @nickvigilante.

Ah. We missed seeing cockroachdb/docs#14376 in the initial investigation.

Yes, it's possible for multiple release notes to be present in a commit and for multiple commits in a PR to have release notes. Take a look at the General structure of a commit message section of the Git Commit Messages wiki page and the Release notes wiki page for information on how release notes work.