Filter based on issue type #1187
Labels
feature request
New feature or request to improve the current logic
Comments
Bibo-Joshi
added
feature request
|
Hello @Bibo-Joshi, |
|
We are switching over to issue types as well over in zed.dev's issue tracker - would love to have this configuration option. |
|
This is very much needed, otherwise we have duplicates for labels and types now. |
|
One thing to note is that GitHub's REST API doesn't even support filtering by type, as far as I can tell. So until that lands, getting that feature in the stale action is totally blocked. https://github.com/orgs/community/discussions/140874#discussioncomment-11582660 |
JasonStoltz
added a commit
to elastic/eui
that referenced
this issue
Mar 25, 2025
We're moving away from the `bug` label and `task` label in favor of Github Issue types. Stale bot does not yet support Issues Types: actions/stale#1187 This would impact the majority of bugs in our backlog. While not immediately, they will get a stale label and ultimately auto-closed within the next couple of months. Are we OK with that? Should we consider adding some sort of "pinned" label to save these bugs?
|
Looks like they've added Issue Type to the Reset API. |
|
Any progress with this one? I think there are no blocking things with it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Introduce a parameter
only-issue-typesthat ensures that only issues of a specific type are set to stale and closed.Justification:
With the introduction of types, GitHub as given organizations a new issue attribute that can be used for categorization/classification of issues. For different issue types it would be desirable to have different stale settings just like we currently can have for labels. E.g. in my organization, we'll be using the new issue type for separating questions from feature requests. Questions should go stale faster.
Are you willing to submit a PR?
I'm open to try so, but will need some pointers, especially on testing. I'm not familia with TypeScript (or very familiar with JS at all …)
The text was updated successfully, but these errors were encountered: