Open klassenserver7b opened 1 month ago
Hi @klassenserver7b, thanks for reaching out.
I have already put in place some checks and related tests that are meant to prevent this from happening so I wonder how this happened in your case. My guess is that the action is not able to identify you as the author of the PR. Is there something specific about this PR or the workflow setup that could explain why it's behaving this way?
I have no clue because I opened the PR manually on github.com. The login name should definitely be no problem that way. I may investigate this further and reach out again.
I just tried once more with similar settings but I couldn't reproduce:
Run pozil/auto-assign-issue@v1
with:
assignees: pozil, other1, other2
allowSelfAssign: true
abortIfPreviousAssignees: false
removePreviousAssignees: false
allowNoAssignees: false
teamIsPullRequestReviewer: false
repo-token: ***
Setting assignees for PR 11: ["pozil","other1","other2"]
Setting reviewers for PR 11: ["other1","other2"]
The action fails because other1
and other2
are not real users but the point is that I'm removed from the list of reviewers as expected...
I use your action on my project, but when I make a PR, it tries to request a review from me. This is obviously prohibited, as you mention in the annotation to
allowSelfAssign
-parameter (This flag is ignored when working with PRs as self assigning a PR for review is forbidden by GitHub.
) But especially if you ignore this flag, there should be some logic prohibiting my self assignment.Context: The repo is created by me in an organization created by me.
My runner log: