-
Notifications
You must be signed in to change notification settings - Fork 24
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] Avoid the old, untracked issue. #30
Labels
good first issue
Good for newcomers
Comments
I think this is quite important for us to handle issues as soon as possible. However, I think 30 days is a little bit short, how about 60 days, two months? @Frankzhaopku |
@allencloud I suppose this should be configurable, I will consider this during PR review. |
Stephlan
pushed a commit
to Stephlan/pouchrobot
that referenced
this issue
Jul 10, 2018
Add backend interface for closing 30-day expired issues.
For this issue, I think the following steps could do it:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The user or developer will create issue to PouchContainer for issue report or something. For some issues, with some reason, we cannot reproduce the issue or has it fixed. However, the issue will look like orphan in the system.
For this reason, I propose to add the functionality in the PouchRobot to close the issue if no-one comments in 30 days. If PouchContainer still has the issue, this action will let the owner know that there is one orphan need help.
The text was updated successfully, but these errors were encountered: