I was reviewing an open issue (https://bugs.python.org/issue36338) and seeing there was a merged PR, I wanted to check with my test and close the issue after validation. Unfortunately, my test failed because the associated PR was not related to the issue.
How can we avoid this situation?
When bedevere adds the url of the bpo issue, maybe it could also add the title of the issue (from bpo) in the PR like that
https://bugs.python.org/issue36338 : urlparse of urllib returns wrong hostname
and the double check from the contributor|core-dev could be easier.
With the titles of the PR and the issue, we could check if there is a matching or not.
PR: "bpo-36368: Ignore SIGINT in SharedMemoryManager servers".
BPO: "urlparse of urllib returns wrong hostname"
Is it relevant? and what do you suggest for this kind of situation?
Ah, ok, it’s good to know that we can pull the issue title easily.
However, I’m don’t think copying over bpo title to GitHub PR is good idea.
What if the bpo title was changed after the PR was created?
When I have written my initial message, I have thought about this issue. I haven’t yet read the content of your link but maybe there is a solution, thank you for the link.