Add Discussion label workflow #11300
Merged
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
eavanvalkenburg
approved these changes
Apr 2, 2025
TaoChenOSU
approved these changes
Apr 2, 2025
glorious-beard
pushed a commit
to glorious-beard/semantic-kernel
that referenced
this pull request
Apr 6, 2025
### Motivation and Context Right now, we need to manually go through each new discussion item to figure out if it needs certain labels. We also can miss discussion items as we don't have the "triage" label applied automatically like we do for issues. We have some discussion categories where users can post for help -- specifically "General," "Q&A," and "Ideas." Other discussion categories don't warrant "triage," "python," or ".NET" labels. <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description This PR adds a "Label Discussions" workflow that runs when new discussions are created as part of General, Ideas, or Q&A, that leverages GitHub's GraphQL API. This was tested in my SK fork for new issues, and it properly adds the appropriate label based on the content of the discussion item. This should help make sure we don't miss any discussion item as we look through them during triage. <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄
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.
Motivation and Context
Right now, we need to manually go through each new discussion item to figure out if it needs certain labels. We also can miss discussion items as we don't have the "triage" label applied automatically like we do for issues. We have some discussion categories where users can post for help -- specifically "General," "Q&A," and "Ideas." Other discussion categories don't warrant "triage," "python," or ".NET" labels.
Description
This PR adds a "Label Discussions" workflow that runs when new discussions are created as part of General, Ideas, or Q&A, that leverages GitHub's GraphQL API. This was tested in my SK fork for new issues, and it properly adds the appropriate label based on the content of the discussion item.
This should help make sure we don't miss any discussion item as we look through them during triage.
Contribution Checklist