-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Update bedevere for the GitHub migration #418
Comments
I've just opened the PR for handling the new labels: #419 |
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? |
I think so. |
The reason to change from the full link to 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. |
Expect gh- issue number in titles. Remove logic for adding bpo url in the body. Validate that the GH- issue is indeed an issue, not PR Closes #418
Expect gh- issue number in titles. Remove logic for adding bpo url in the body. Validate that the GH- issue is indeed an issue, not PR Closes #418
Oh I have started removing the Updating old prs that has |
Expect gh- issue number in titles. Remove logic for adding bpo url in the body. Validate that the GH- issue is indeed an issue, not PR Closes #418
Currently bedevere does the following things:
bpo-*
form to enable redirectspython/cpython
core-workflow#432cc @brettcannon
The text was updated successfully, but these errors were encountered: