You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason to change from the full link to bpo-* (or better just add bpo-* next to it) is that bpo-* can automatically redirect to the right GH issue without having to go through the bpo issue manually. That's also why I was asking if it's possible to update old links -- if not, people will have to deal with a click more and some extra loading time, but it's not the end of the world.
It might be useful to wait a few days to disable the feature, to leave some time for people to adjust to the new workflow (some might still use the bpo ID if they are not sure what todo). After that the feature can be removed, unless you want to check that the PR is linked to an existing GH issue instead.
Activity
Mariatta commentedon Mar 24, 2022
I've just opened the PR for handling the new labels: #419
I noticed the bpo- check while working on it. I'll try to work on a PR.
Mariatta commentedon Mar 24, 2022
I'm planning to just remove this functionality completely, so that bedevere will no longer be appending issue link at the end. Is this ok?
brettcannon commentedon Mar 24, 2022
I think so.
ezio-melotti commentedon Mar 24, 2022
The reason to change from the full link to
bpo-*(or better just addbpo-*next to it) is thatbpo-*can automatically redirect to the right GH issue without having to go through the bpo issue manually. That's also why I was asking if it's possible to update old links -- if not, people will have to deal with a click more and some extra loading time, but it's not the end of the world.It might be useful to wait a few days to disable the feature, to leave some time for people to adjust to the new workflow (some might still use the bpo ID if they are not sure what todo). After that the feature can be removed, unless you want to check that the PR is linked to an existing GH issue instead.
Support GitHub Issues and drop b.p.o
Support GitHub Issues and drop b.p.o
Mariatta commentedon Mar 25, 2022
Oh I have started removing the
bpo-thing altogether before I saw your comment. (see #420)Updating old prs that has
bpo-in it can perhaps be done using one-off script.Support GitHub Issues and drop b.p.o (#420)