Skip to content
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

[Feature] Only mark issues stale if a maintainer was the last to comment #346

Closed
tnorling opened this issue Mar 3, 2021 · 7 comments
Closed

Comments

@tnorling
Copy link

tnorling commented Mar 3, 2021

It would be great if the stale-bot ignored issues that are waiting for a maintainer to respond. Sometimes it takes us a while to get back to customers and we don't want issues auto-closed if we are the reason the issue is stale. One way you could potentially do this is by reading the repo's CODEOWNERS file to get a list of usernames to check for.

@C0ZEN
Copy link
Contributor

C0ZEN commented Mar 3, 2021

@tnorling to sums up, you wish to avoid to stale when there is no comment from a user considered as "maintainer", right?

@tnorling
Copy link
Author

tnorling commented Mar 3, 2021

I wish to avoid labeling as stale/closing when the most recent comment is not from a maintainer.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 3, 2021

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the Stale label Apr 3, 2021
@C0ZEN
Copy link
Contributor

C0ZEN commented Apr 3, 2021

up

@github-actions github-actions bot removed the Stale label Apr 4, 2021
@github-actions
Copy link
Contributor

github-actions bot commented May 4, 2021

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the Stale label May 4, 2021
@C0ZEN
Copy link
Contributor

C0ZEN commented May 4, 2021

up

@tnorling
Copy link
Author

We ended up switching to an internal tool to handle this use case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants