chore: add stale bot

[jsjoeio]

@jawnsy brought this up the other day. Then GitHub mentioned we should it so I thought why not 🤷‍♂️

I will take responsibility if it goes horribly wrong 😂

The way this works is we have a stale.yml under .github which is the configuration and then @jawnsy enabled Stale bot it at the cdr org level.

Fixes N/A

[github-actions]

✨ Coder.com for PR #4048 deployed! It will be updated on every commit.

• Host: https://codercom-8iq02rkwf-codercom.vercel.app/docs/code-server
• Last deploy status: success
• Commit: dbd1a22
• Workflow status: https://github.com/cdr/code-server/actions/runs/1172365315

[jawnsy]

I think it's better to use the stale config and have the external Stale app take care of this. A common config across our repos also makes it easier for someone to switch between our repos

[jsjoeio]

Good call!

[codecov]

Codecov Report

Merging #4048 (eed4e64) into main (6c6446f) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##             main    #4048   +/-   ##
=======================================
  Coverage   63.51%   63.51%           
=======================================
  Files          36       36           
  Lines        1872     1872           
  Branches      379      379           
=======================================
  Hits         1189     1189           
  Misses        580      580           
  Partials      103      103           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c6446f...dbd1a22. Read the comment docs.

[Lemmingh]

I guess you forgot to set exemptLabels and exemptMilestones. An On Deck bug is closed:
#1105

[jsjoeio]

@Lemmingh thanks for pointing that out!

I guess we should add that. If no one responds though, it's still probably stale and makes sense to close, but I'll open an issue to do this.

[bpmct]

Does that mean #33 will be considered stale at some point?

[jsjoeio]

@bpmct yes if there is no activity for 180 days!