Add stale bot

[AGMETEOR]

What does this change

Introduces a stale bot that marks issues and PRs as stale after some time

What issue does it fix

Closes #2796

Notes for the reviewer

This implementation uses https://github.com/actions/stale .
We need to discuss certain things, like the text for the stale labels, after how long to mark as stale, close or leave PRs and issues open once they go stale?

Checklist

• Did you write tests?
• Did you write documentation?
• Did you change porter.yaml or a storage document record? Update the corresponding schema file.
• If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Reviewer Checklist

• Comment with /azp run test-porter-release if a magefile or build script was modified
• Comment with /azp run porter-integration if it's a non-trivial PR

[troy0820]

Not sure if getporter has this but using this, this token would have to be set.

[AGMETEOR]

Hey @troy0820 thanks for the review. I took this from another yaml file in this project

porter/.github/workflows/close-issues.yaml

Line 19 in be5c66a

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Not sure if it's set. Is it possible to confirm if it's indeed set?

[schristoff]

^^ was gonna suggest that it be this

[schristoff]

Let's set up some rules around closing issues, and we'll follow how the k8s stale bot does things.
Looking at this comment from the bot
Let's go ahead and take their lead on the timelines they set, as well as labels, and I like having the bot comment on the timelines. So.. let's just take the whole thing lol.

Bot should comment basically the same thing as the comment. I'll copy the comment so it's easier to see here:

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged 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
You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close

/lifecycle stale

(we can't don't have their triage for help or sigs so I removed those two bottom lines) replace kubernetes with porter and we should be g2g

[schristoff]

Heya! Just wanted to check in and see if there's any assistance I can provide to get this merged! Thank you again for all your work.

[AGMETEOR]

Hi @schristoff just haven’t been feeling well. Will finish this off before this week ends.

[schristoff]

No rush of course, your health comes first (and work, family, all those other things!). Feel better soon!

[AGMETEOR]

Heya! Just wanted to check in and see if there's any assistance I can provide to get this merged! Thank you again for all your work.

Just made some changes. I used the actions/stale workflow to compose together steps to handle the requirements for this bot. Now, I need to find a way to test it.

[troy0820]

@AGMETEOR Your DCO isn't set up again. Can you run mage SetupDCO or go run mage.go SetupDCO to fix that?

[AGMETEOR]

Got sidetracked a bit. But I am back working on this week

[schristoff]

After many discussions, here's what we've decided on:

1. An auto-labeler
2. Creating issue response templates
3. Creating a triage.md and setting healthy and reasonable expectations on when we will triage.

I'm closing this for now and I'm going to be opening a triaging issue :)