fix(docs): Update KEP for AI Issue Triage#13530
Open
alyssacgoins wants to merge 1 commit into
Open
Conversation
…arking /ready. Signed-off-by: Alyssa Goins <agoins@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the proposal doc to replace the /good-first-issue gate with a /ready label and adjusts the described triage/gatekeeper workflow accordingly.
Changes:
- Renames references from
/good-first-issueto/readythroughout the proposal, including the auto-close message. - Updates the “beginner-friendly issue” workflow steps to include AI feedback + maintainer review before marking issues
/ready. - Adds an inline TODO noting that the workflow section still needs updating.
| 1. This proposal does not enhance support for the PR review process. It aims to reduce extraneous PRs. | ||
|
|
||
| ## Proposal | ||
| This KEP proposes a two-part approach: a GitHub Action workflow to label good first issues, and a GitHub Action workflow to validate that PRs raised by new contributors link an issue with this label. |
Comment on lines
+27
to
+28
| ### I. Introduce '/ready' label for beginner-friendly issues | ||
| #TODO: this section needs to be updated with updated workflow |
Comment on lines
+30
to
+32
| 1. Utilize `gpt-4o-mini` with GH Models API to analyze issue for scope, context, guidance and complexity and decide if the issue contains enough information to be resolved by a contributor (new or otherwise). | ||
| Also identify which section of the codebase the issue targets (e.g., frontend, backend, testing, chore) | ||
| 2. Comment on the issue with the generated feedback. |
| @modichika proposes the following workflow to validate beginner-friendly issues in the following PR: https://github.com/kubeflow/pipelines/pull/13372 | ||
| 1. Utilize `gpt-4o-mini` with GH Models API to analyze issue for scope, context, guidance and complexity and decide if the issue is a good candidate for first-time contributors. | ||
| 2. If the issue is a good candidate, it is labeled `/good-first-issue` | ||
| 1. Utilize `gpt-4o-mini` with GH Models API to analyze issue for scope, context, guidance and complexity and decide if the issue contains enough information to be resolved by a contributor (new or otherwise). |
This file contains hidden or 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
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.
Description of your changes:
Update KEP with the following key details:
/good-first-issueto/readyChecklist: