ci(framework) Add file to auto-assign GitHub Issues to developer #4817
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
WilliamLindskog
requested review from
Robert-Steiner,
tanertopal and
danieljanes
as code owners
WilliamLindskog
changed the title
WilliamLindskog
force-pushed
the
issues-workflow
branch
from
86cf2e7 to
ac77abc
Compare
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.
Issue
Currently, we manually assign GitHub Issues to Flower Developers.
Description
The process is manual and it would be good to have issues being automatically assigned to a developer (in Flower).
Related issues/PRs
N/A
Proposal
Add auto-assign to William.
Explanation
Currently, we only need to assign it to William Lindskog who can see if other developers' help is needed to resolve issue.
Checklist
#contributions)Any other comments?
N/A