i'm a bit -0 on this. I agree that a lot of stale issues deserve closing, but others are really long term goals. I do not want to block this great idea but am just a bit worried about other great ideas getting lost. So I would propose to tag anything we close or not remove the stale tag, so these can be easily found. I am not worried too much about PRs, just issues.
On the other hand, we can always remove the gha again, so maybe we should install it and see if it works for us. On Wed, Feb 14, 2024 at 4:49 AM Kiran Chavala <kiran.chav...@shapeblue.com> wrote: > > Good idea Vishesh > > +1 for using Githubactions > > Regards > Kiran > > From: Vishesh Jindal <vishesh.jin...@shapeblue.com> > Date: Tuesday, 13 February 2024 at 6:33 PM > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: [DISCUSS] Closing issues & PR after a certain time > Hi everyone, > > I was going through the issues and PRs, and I noticed that a lot of them are > really old and some of them are waiting for the original author to reply. > > I wanted to discuss if we should add a github action > (https://github.com/marketplace/actions/close-stale-issues) for auto closing > the issues and PRs after a certain time. > > From the github actions' documentation, this is how it works: > > * Add a label "Stale" on issues and pull requests after 60 days of > inactivity and comment on them > * Close the stale issues and pull requests after 7 days of inactivity > * If an update/comment occur on stale issues or pull requests, the stale > label will be removed and the timer will restart > > Instead of using the defaults, I would like to: > > * > mark the issue/PR stale after 90 days > * > close the stale issue/PR after 30 days > > Let me know if this sounds good. I will create the PR to set this up. > > Regards, > Vishesh > > > > > > > > -- Daan
