Skip to content

Bedevere should label "awaiting merge" after a core review #584

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

Closed
hugovk opened this issue Sep 23, 2023 · 3 comments
Closed

Bedevere should label "awaiting merge" after a core review #584

hugovk opened this issue Sep 23, 2023 · 3 comments
Assignees
Labels

Comments

@hugovk
Copy link
Member

hugovk commented Sep 23, 2023

Steps to reproduce

  1. PR has "awaiting review" label
  2. A core dev approves it

Actual result

Bedevere removes "awaiting review" and adds "awaiting core review"

(This is what should happen when a non-core dev approves.)

Expected result

Bedevere removes "awaiting review" and adds "awaiting merge"

For example:

image

And:

image

See also

State diagram at https://github.com/python/bedevere#pr-state-machine

@hugovk hugovk added the bug label Sep 23, 2023
@Mariatta Mariatta self-assigned this Sep 23, 2023
@Mariatta
Copy link
Member

I'll take a look tomorrow.

@pradyunsg
Copy link
Member

@Mariatta and I investigated this yesterday, and this has been resolved.

For posterity: The bot was recently migrated from a GitHub (bot) account to a GitHub App. During this migration, insufficient permissions were provided to the bedevere GitHub App -- it did not have the permission to query the membership to teams within the python organisation. This meant that the bot could not determine who is a core team member, and would label PRs as if everyone reviewing PRs is not a core developer.

Adding the relevant permission resolved this issue.

@hugovk
Copy link
Member Author

hugovk commented Oct 13, 2023

Thanks both!

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

No branches or pull requests

3 participants