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

auto-close "rotten" issues per fejta-bot k8s example #1011

Open
jctanner opened this issue Sep 3, 2018 · 6 comments

Comments

@jctanner
Copy link
Member

commented Sep 3, 2018

kubernetes/minikube#2527 (comment)

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
--

We should consider as a point of project governance that inactive issues aren't being worked.

@gundalow

This comment has been minimized.

Copy link
Collaborator

commented Sep 4, 2018

Interesting workflow. This seems to be closing any any issue older than 90 (or 120 days).

If anyone is working on a fix for the issue do we want to require/enforce:

  • they are assigned
  • a comment along the lines of "I'm working on this"?

@jctanner how did you imagine the workflow looking like?

@gundalow gundalow added this to Backlog in Bot Work Sep 6, 2018
@jctanner jctanner added the governance label Jul 16, 2019
@webknjaz

This comment has been minimized.

Copy link
Member

commented Jul 23, 2019

@webknjaz

This comment has been minimized.

Copy link
Member

commented Jul 23, 2019

they are assigned

FTR modern GitHub allows assigning issues to any users who commented them ever.

@dessant

This comment has been minimized.

Copy link

commented Aug 14, 2019

@webknjaz, I think Stale is a better fit for this use case, Lock Threads operates on issues that were already closed.

@webknjaz

This comment has been minimized.

Copy link
Member

commented Aug 14, 2019

@dessant that's a different case but related. Originally I wanted to replace what @sivel's been doing manually.

@geerlingguy

This comment has been minimized.

Copy link

commented Sep 23, 2019

We discussed this at AnsibleFest Atlanta during the Community Summit. The in-room consensus was to use a model similar to K8s' bot, where:

  • After 30d with no activity, open feature request is marked 'stale'
  • After 90d with no activity, open feature request is closed

The bot would ideally also be able to interpret issue-related comments like close/notstale/etc. like https://github.com/kubernetes/test-infra/tree/master/prow#bots-home

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Bot Work
  
Backlog
5 participants
You can’t perform that action at this time.