-
-
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
Renaming issues/PRs incorrectly changes awaiting change review
and awaiting merge
to awaiting review
#556
Labels
Comments
oops, you're right, this handler is doing way more than it was intended! |
@itamaro Could you submit a PR, please? |
itamaro
added a commit
to itamaro/bedevere
that referenced
this issue
May 6, 2023
pythongh-555 introduced the PR edited handler to handle draft PRs. The implementation was over-reaching, and triggered on any edited events (including renaming PR). This PR fixes that by removing the PR-edited handler and replacing it with two more specific handlers that more narrowly match the original intent, namely, respond to changes in the draft state of the PR (publish / unpublish). Fixes pythongh-556
of course |
itamaro
added a commit
to itamaro/bedevere
that referenced
this issue
May 6, 2023
JelleZijlstra
pushed a commit
that referenced
this issue
May 10, 2023
gh-555 introduced the PR edited handler to handle draft PRs. The implementation was over-reaching, and triggered on any edited events (including renaming PR). This PR fixes that by removing the PR-edited handler and replacing it with two more specific handlers that more narrowly match the original intent, namely, respond to changes in the draft state of the PR (publish / unpublish). Fixes gh-556
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While changing
bpo-
togh-
I noticed that Bedevere makes forbidden transitions in response:According to README,
awaiting review
has no incoming conditions:I suspect the bug is here, in a handler of PR/issue modifications introduced in gh-555:
bedevere/bedevere/stage.py
Lines 127 to 131 in 0f350ce
We need to check whether assignment of
Blocker.core_review
orBlocker.review
is allowed before executing theelse
branch.Ideally (for some distant future) we need to move tag management into a separate
.py
file that reads existing tags, checks if a new one is applicable, and removes the old ones. However, I have no free time to do it currently (because it requires massive modification of both reactors and their tests).cc @itamaro
The text was updated successfully, but these errors were encountered: