Wizard automation: check for response on "info needed" issue & close

merelcht commented 3 weeks ago

Description

Any ticket labelled with support: need more info will be closed automatically after 14 days if the author doesn't respond. The label is removed if the author does respond.

Development notes

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

[ ] Read the contributing guidelines
[ ] Signed off each commit with a Developer Certificate of Origin (DCO)
[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the RELEASE.md file
[ ] Added tests to cover my changes
[ ] Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

rashidakanchwala commented 2 weeks ago

I am confused if we should close them or not? Can we not automate the closing part, as I feel it requires some manual intervention.

merelcht commented 2 weeks ago

I am confused if we should close them or not? Can we not automate the closing part, as I feel it requires some manual intervention.

This GH action will close the ticket automatically if there's not response from the author after 14 days.

rashidakanchwala commented 2 weeks ago

That makes sense. What I meant was that I feel undecided about automatically closing the issue in 14 days. It’s not uncommon for Viz-related community issues to remain open longer, often requiring multiple follow-ups to get user input. However, if you and @astrojuanlu are happy with the automatic 14-day closure, I’m ok with it too.

merelcht commented 2 weeks ago

That makes sense. What I meant was that I feel undecided about automatically closing the issue in 14 days. It’s not uncommon for Viz-related community issues to remain open longer, often requiring multiple follow-ups to get user input. However, if you and @astrojuanlu are happy with the automatic 14-day closure, I’m ok with it too.

We can definitely make it longer! Or set a different limit for each repo. We'll have to add each action to the repos separately anyway.

astrojuanlu commented 2 weeks ago

On second thought, wondering if 14 days might be too aggressive and we could bump it to 28.

merelcht commented 2 weeks ago

Of course, I'll do that now!

kedro-org / kedro