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

Issue closed close period days after reopen #351

Closed
TheOneRing opened this issue Mar 4, 2021 · 5 comments · Fixed by #352
Closed

Issue closed close period days after reopen #351

TheOneRing opened this issue Mar 4, 2021 · 5 comments · Fixed by #352

Comments

@TheOneRing
Copy link

The issue owncloud/client#8365 was closed automatically 8 days after it was reopened.
Without any previous stale message

@C0ZEN
Copy link
Contributor

C0ZEN commented Mar 4, 2021

@TheOneRing I added a reproduction in the tests and basically the culprit here is that the issue was reopened without removing the stale label.
I was not aware of this and in fact I think it's awesome because it can close #188 IMO.

I thought that only the updateAt/last comment was a requirement to know if it's stale or not but in fact having a stale label influence the action and has a better priority.
What do you think?

On the other hand, it can be convenient to have eventually a feature which remove the stale label for you when the issue/PR is reopen but in that case opening a new issue for that would be better.

@hross hross closed this as completed in #352 Mar 5, 2021
@TheOneRing
Copy link
Author

Yes but I would expect a message that #xxx is going to be closed in 7 days because of reasons :)

@C0ZEN
Copy link
Contributor

C0ZEN commented Mar 5, 2021

@TheOneRing IMO the best option to solve this is to remove the stale label after reopening.
Basically reopening means that it's a keeper so it's kinda opposite to letting it be stale.
It could be made with an option and if disabled instead send once again the message saying that it will be closed in x days.
Is this ok for you?

@TheOneRing
Copy link
Author

Option two sounds handy, as this behavior should also cause a message on manually labeled issue?

@C0ZEN
Copy link
Contributor

C0ZEN commented Mar 9, 2021

@TheOneRing yes, I think the only missing piece is the comment when you manually label as stale.
And I also think also that the best solution would be to remove the stale label once closed.

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

Successfully merging a pull request may close this issue.

2 participants