docs: document issue lifecycle labels and roadmap sequencing - #2524
Merged
Conversation
krishicks
requested review from
a team,
derekwaynecarr,
maxamillion and
mrunalp
as code owners
July 28, 2026 16:22
|
🌿 Preview your docs: https://nvidia-preview-pr-2524.docs.buildwithfern.com/openshell |
pimlock
reviewed
Jul 29, 2026
pimlock
left a comment
pimlock
left a comment
Collaborator
There was a problem hiding this comment.
This looks good IMO, I haven't reviewed all the small changes, my assumption is the overall approach was to define the new process (the issue-lifecycle doc), give that to the agent to update all existing skills/documentation around this?
Once this lands, we'll need to migrate some of the existing labels, right? E.g. the state:... -> agent:....
krishicks
force-pushed
the
hicks/push-korllpnmymol
branch
2 times, most recently
from
July 29, 2026 23:08
682bd79 to
3cdfeec
Compare
matthewgrossman
previously approved these changes
Jul 30, 2026
matthewgrossman
left a comment
matthewgrossman
left a comment
Contributor
There was a problem hiding this comment.
overall lgtm, also feels reasonable to try out and adjust the process as we find parts we like/don't like (like we're doing now!)
krishicks
enabled auto-merge
July 30, 2026 17:58
Add a published Issue Triage and Lifecycle page and align AGENTS.md, CONTRIBUTING.md, README.md, the PR template, and the issue-handling skills on the state:*/agent:* label model. Signed-off-by: Kris Hicks <khicks@nvidia.com>
krishicks
force-pushed
the
hicks/push-korllpnmymol
branch
from
July 30, 2026 18:12
3cdfeec to
03bf078
Compare
pimlock
approved these changes
Jul 30, 2026
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
3 participants
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.
Summary
Add a published Issue Triage and Lifecycle page and align AGENTS.md, CONTRIBUTING.md, README.md, the PR template, and the issue-handling skills on the state:/agent: label model.
This is meant to make it easier for us to manage the open issues and PRs in the project. Presently it's not easy to know which issues are validated and/or accepted, for example. This also clarifies the state machine for issues that are going to be owned by an agent.
Related Issue
Changes
Testing
mise run pre-commitpassesChecklist