Repository navigation
Link to GitHub PR from bpo emails #35
Description
Activity
- The 70 only refers to pull_request item of the tracker, i.e. https://bugs.python.org/pull_request70
The actual PR number is different, as you can see from the link (in this case is bpo-29481: add versionadded 3.6.1 to typing.Deque docs cpython#107). - These mails are automatically generated, and I'm not aware of a way to change them and insert the link. It should be possible, but probably it's not too straightforward, and it might not be worth the effort.
Reacted by Berker Peksag- The 70 only refers to pull_request item of the tracker, i.e. https://bugs.python.org/pull_request70
Thanks for the info, @ezio-melotti
If there's no straightforward way to do it, then let's not bother for now.I'm reopening this, as the status quo is genuinely confusing when one PR references multiple issues - each email has a different numeric identifier for the PR, even if they're all related to the same PR. (I'd be surprised if it ever happens again to the degree it did when the draft NEWS generation PR was closed, but I'd also be surprised if it never happens at all)
Rather than attempting to customise these emails directly, would it possible to turn off email notifications for PR additions and state changes entirely, and instead inject more meaningful comments describing the state change?
If you want to continue the discussion I'd suggest moving it to the meta-tracker:
http://psf.upfronthosting.co.za/roundup/meta/issue624
When someone creates a pull request that links to a bpo issue, there would be email sent to the issue subscribers / nosy list, for example:
70here refer to GitHub pull request number 70? (eg Add Travis CI and Codecov badges to README cpython#70)+70, can it be a link to the said pull request?Thanks :)