Skip to content
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

msftbot could be taught about the source-generator label. #49

Open
teo-tsirpanis opened this issue Mar 2, 2022 · 3 comments
Open

msftbot could be taught about the source-generator label. #49

teo-tsirpanis opened this issue Mar 2, 2022 · 3 comments

Comments

@teo-tsirpanis
Copy link

teo-tsirpanis commented Mar 2, 2022

msftbot could be taught to apply the source-generator label to:

  • Issues that include certain keywords in a similar fashion to how it predicts area labels and learns from manually added ones.
  • PRs that primarily change files inside src/libraries/*/gen/.
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@ghost
Copy link

ghost commented Mar 2, 2022

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

"source generator files" can be defined as these in src/libraries/*/gen/.

Author: teo-tsirpanis
Assignees: -
Labels:

area-Meta, untriaged

Milestone: -

@teo-tsirpanis teo-tsirpanis changed the title msftbot could be taught to automatically apply the source-generator label to PRs that primarily change source generator files. msftbot could be taught about the source-generator label. Mar 2, 2022
@danmoseley danmoseley transferred this issue from dotnet/runtime Jul 6, 2022
@danmoseley
Copy link
Member

Transfering to https://github.com/dotnet/issue-labeler as this is really an ask for the ability to predict and apply more than "area-" labels, depending on the repo.

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

No branches or pull requests

2 participants