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
chore: Exclude topic/core
issues/PRs from Stale Bot
#7788
chore: Exclude topic/core
issues/PRs from Stale Bot
#7788
Conversation
@@ -52,6 +52,8 @@ jobs: | |||
days-before-pr-close: "${{ env.DAYS_BEFORE_PR_CLOSE }}" | |||
days-before-pr-stale: "${{ env.DAYS_BEFORE_PR_STALE }}" | |||
exempt-all-milestones: true | |||
exempt-issue-labels: "topic/core" |
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.
maybe even some label like "prevent-stale" to prevent stable bot on non-core topics
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.
No, I want meaningful labels that serve real purpose of cataloguing stuff, so I prefer not to add label just for ignoring - it's better to use multiple explicit labels for each Stale Bot's option if needed.
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.
approved and disabled auto-merge. check my comment and decide which way to go. both are OK for me.
5bbaa53
to
fbe81b7
Compare
Issues/PRs related to core features should be excluded from Stale Bot as these are part of internal vision for project development. We should apply
topic/core
label when we agree that something must be done in the Fixer's engine/architecture/design and keep it open (of course reviewing these issues from time to time is highly recommended).