-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add stale action for open issues #36468
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
- uses: actions/stale@v5 | ||
with: | ||
any-of-labels: "community" | ||
exempt-issue-labels: "frozen" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like maybe there are some more exempt ones here and below. The ones that comes to mind the ones that are still on the roadmap. https://github.com/orgs/airbytehq/projects/37/views/1
We could run scripts to tag those automatically.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if there are multiple tags here like roadmap
and somethingelse
or there should just be one like evergreen
or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Roadmap issues are usually created by the Airbyte team and won't have the community
label.
The any-of-labels
ensure this action will be applied to only community
labeled issues any other it's internal won't be applied.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is frozen
exempt though. Just so it doesn't compete with the other timeline? What about ones from the community that are ebing worked on. Maybe those get assigned and stuff so they don't get stale?
steps: | ||
- uses: actions/stale@v5 | ||
with: | ||
any-of-labels: "frozen" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case it only apply stale action to issues were triaged by the engineering teams.
Roadmap and other issues I don't think will be enter this workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, whatever you think. Go for it.
- uses: actions/stale@v5 | ||
with: | ||
any-of-labels: "community" | ||
exempt-issue-labels: "frozen" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is frozen
exempt though. Just so it doesn't compete with the other timeline? What about ones from the community that are ebing worked on. Maybe those get assigned and stuff so they don't get stale?
This PR adds 2 stale actions: