Document an issue triage workflow for the repository #3394
+159
−9
Conversation
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
dehaansa
commented
Apr 17, 2025
| @@ -0,0 +1,15 @@ | |||
| name: Blank issue | |||
There was a problem hiding this comment.
This mimics the blank issue for github as well as possible while also adding the expected label.
dehaansa
commented
Apr 17, 2025
| @@ -12,7 +12,7 @@ jobs: | |||
| steps: | |||
| - uses: actions/stale@5bef64f19d7facfb25b37b414482c7164d639639 # v9.1.0 | |||
| with: | |||
| days-before-stale: 30 | |||
| days-before-stale: 90 | |||
There was a problem hiding this comment.
I'm open to changing this back to 30, I wanted to focus on reversing the mechanism - all things need attention (triage) until they have been reviewed.
|
I'm going to update templates to add the ability to select a component from a dropdown if relevant. |
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.
PR Description
In order to better manage the landscape of issues raised against the Alloy repository, I'd like to propose an issue triage workflow to help define the triage process. A more consistent triage process will make it easier for team members to step in and do a small amount of triage and leave the issue landscape in a better place than they found it. It should also enable us to identify long-term trends on issues.