Add a worklow to potentially deal with stale PR's and Issues

[mviswanathsai]

Explanation

This PR is to discuss, finalize and implement a strategy to manage stale issues and PRs lifecycle in the kyverno repo.

Related issue

Milestone of this PR

Documentation (required for features)

My PR contains new or altered behavior to Kyverno.

• I have sent the draft PR to add or update the documentation and the link is:

What type of PR is this

Proposed Changes

To add a github worklow to automate /semi-automate the process.

Proof Manifests

Checklist

• I have read the contributing guidelines.
• I have read the PR documentation guide and followed the process including adding proof manifests to this PR.
• This is a bug fix and I have added unit tests that prove my fix is effective.
• This is a feature and I have added CLI tests that are applicable.
• My PR needs to be cherry picked to a specific release branch which is .
• My PR contains new or altered behavior to Kyverno and
  • CLI support should be added and my PR doesn't contain that functionality.

Further Comments

moved to #9857

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 33.15%. Comparing base (d737138) to head (d9ea5ec).
Report is 29 commits behind head on main.

❗ Current head d9ea5ec differs from pull request most recent head ebee6f7. Consider uploading reports for the commit ebee6f7 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9788   +/-   ##
=======================================
  Coverage   33.15%   33.15%           
=======================================
  Files         345      345           
  Lines       23634    23634           
=======================================
  Hits         7836     7836           
  Misses      14952    14952           
  Partials      846      846           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[realshuting]

Thanks for the PR @mviswanathsai ! It is worth checking how Kubernetes does this.

[mviswanathsai]

Hey, Shuting! @JimBugwadia also advised me to look into Kubernetes. I just made this PR as a placeholder for further discussions.
Kubernetes follows the method outlined here. They run a docker image for the robot, the metrics etc.
We could try and use the same I think, I could not find much info about it though.
Here is the config file they use.

[mviswanathsai]

In the slack discussion, I have also linked some discussions on the Kubernetes github about the behavior of the bot itself. It might be worth checking out!

[realshuting]

Triaging issues:

        This bot triages issues according to the following rules:
        - After 90d of inactivity, `lifecycle/stale` is applied
        - After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied
        - After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed

Similar for the PRs:

        This bot triages PRs according to the following rules:
        - After 90d of inactivity, `lifecycle/stale` is applied
        - After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied
        - After 30d of inactivity since `lifecycle/rotten` was applied, the PR is closed

Can we use https://github.com/actions/stale to achieve this?

[mviswanathsai]

I am not sure if we can add add lifecycle/rotten after lifecycle/stale. I will have to look into the docs again to make sure.
Even then, this kind of behavior should be possible with adjusting the limits on the days for stale PRs and issues.

[mviswanathsai]

In addition to that, we can specify labels on issues and PRs that we may not want to be automatically closed by the github action. Something which we might want to consider.

[mviswanathsai]

I am working on a fork of the github stale action which will allow us to add a rotten label also. Though this might not be necessary, and I might be unsuccessful in doing so but I decided to give it a shot. I hope that is not a problem! Please let me know in case we cannot afford that time.

[mviswanathsai]

Update: I've been working on the fork for the past couple of days, I think it works as expected.
I will add a bunch of end-to-end tests and make sure it works as expected in the next few days.

I will also make a pr to the original GitHub stale repo to add the changes as a feature.

[mviswanathsai]

Update: I have created a PR on the github stale action repo.
I will also quickly add a workflow that uses my fork of the repo to let us use the Rotten feature.