Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a page that redirects from bpo to GitHub #17

Closed
ezio-melotti opened this issue Feb 21, 2022 · 3 comments
Closed

Add a page that redirects from bpo to GitHub #17

ezio-melotti opened this issue Feb 21, 2022 · 3 comments
Assignees

Comments

@ezio-melotti
Copy link
Member

As a follow-up of #15, once we have the GitHub id as an attribute in the issue items, we need to create a new script accessible through a URL like bugs.python.org/redirect/BPO-ID that redirects to the corresponding GitHub issue. This could be deployed and tested with fake IDs even before the migration starts.

The plan is to replace #XXXXX issues references with BPO-XXXXX in messages and set GitHub autolinking to point to bugs.python.org/redirect/XXXXX, which in turn redirects back to the corresponding GitHub issue.

@ezio-melotti ezio-melotti added this to To do in GitHub migration via automation Feb 21, 2022
@ezio-melotti ezio-melotti moved this from To do to In progress in GitHub migration Mar 8, 2022
@ezio-melotti ezio-melotti self-assigned this Mar 8, 2022
@ezio-melotti
Copy link
Member Author

This is now live on b.p.o, even though none of the bpo issues (except #2771) have a linked GitHub issue.

To use the redirect, open https://bugs.python.org/issue?@action=redirect&bpo=BPOID, and if the bpo issue exists and has a linked GitHub issue, it will automatically redirect to it. This can be combined with autolinking on the bpo- prefix to link to the redirect page, e.g. bpo-2771.

GitHub migration automation moved this from In progress to Done Mar 9, 2022
@arhadthedev
Copy link

Since each closed gh-migration issue is not just an informational project board entry but is backed by some PR, I believe they should link to corresponding PRs for historical context.

@arhadthedev
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants