Issues auto-assigner #131
Merged
Issues auto-assigner #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olegbespalov
requested review from
mstoykov,
oleiade,
w1kman and
allansson
and removed request for
a team
mstoykov
approved these changes
Jun 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
I've noticed that there some issues in this repo that weren't triaged. As part as the process optimisation I'm introducing a workflow that will auto assign the maintainer based on the keywords (they extracted from the owned repository names).
It's inspired by the one that we have in k6 https://github.com/grafana/k6/blob/master/.github/workflows/issue-auto-assign.yml
Why?
That way we have less chances to miss if there is a feedback/question/bug or whatsoever.