Related Jira tickets referenced in branch commits incorrectly having their deployment status updated

Deploying a merged branch in GitHub is incorrectly reporting all the JIRA tickets mentioned in the branch commits, including commits that were reverted using 'git revert'.

Example scenario:
1. new branch with name 'release/v1.1'
2. add a commit with message='JIRA-0001'
3. add a commit with message='JIRA-0002'
4. revert commit for ticket JIRA-0001, this creates a new commit with message='Revert JIRA-0001'
5. Create PR with title='release/v1.1' and body='JIRA-0002'
6. merge branch
7. deploy merged branch

expected behaviour: only JIRA-0002 reported as deployed

actual behaviour: JIRA-0001 and JIRA-0002 reported as deployed

Is there a way to exclude JIRA-0001 from the deployment status update? Thanks

No files, tests, or entry points are named. Start by tracing how deployment status updates collect Jira tickets from merged branch commits, then reproduce the listed revert scenario; done means only JIRA-0002 is reported as deployed, not the reverted JIRA-0001.

Written by the indexing model from the issue text.