What problem do you want to solve?
Currently the repositories receive AI-assisted PRs which do not follow our PR guidelines, which state that the issue must have the accepted label and the issue is assigned to them.
It creates unnecessary maintenance burden to close the PRs manually and may make assigned developer unsure whether they can raise a PR.
What do you think is the correct solution?
Automatically close the PR if either the issue is not accepted yet or another user is assigned.
This could either be an additional plugin or integrated in the existing "issue-pr-link" plugin.
The advantage of extending the existing "issue-pr-link" is that in the case of a PR close, we would not create a comment on the issue that "this issue is being addressed in pull request #...".
Participation
AI acknowledgment
Additional comments
Maybe the issue message could be "suppressed" if it is possible to delay a plugin or specify the exact order they are run (and they are not run in parallel), as then the "issue-pr-link" could check whether the PR was closed before commenting.
What problem do you want to solve?
Currently the repositories receive AI-assisted PRs which do not follow our PR guidelines, which state that the issue must have the
acceptedlabel and the issue is assigned to them.It creates unnecessary maintenance burden to close the PRs manually and may make assigned developer unsure whether they can raise a PR.
What do you think is the correct solution?
Automatically close the PR if either the issue is not accepted yet or another user is assigned.
This could either be an additional plugin or integrated in the existing "issue-pr-link" plugin.
The advantage of extending the existing "issue-pr-link" is that in the case of a PR close, we would not create a comment on the issue that "this issue is being addressed in pull request #...".
Participation
AI acknowledgment
Additional comments
Maybe the issue message could be "suppressed" if it is possible to delay a plugin or specify the exact order they are run (and they are not run in parallel), as then the "issue-pr-link" could check whether the PR was closed before commenting.