stale automation

[TimothyMothra]

Fixes #2363

Changes

• adding new Stale workflow to automatically close PRs
  • Issues are ignored
  • PRs older that 7 days will be tagged as stale
  • stale PRs will be closed after 7 additional days (14 total).

Adding automation to close stale PRs.
This workflow was copied from https://github.com/open-telemetry/opentelemetry-specification/blob/main/.github/workflows/stale-pr.yaml

Outstanding Questions

• Does this repo require extra permissions for automation to make changes?
  Specification repo uses repo-token: ${{ secrets.GITHUB_TOKEN }} to provide someone's Personal Access Token to the stale automation. May not know if this is needed until we merge this and see it fail :)
• The specification repo is using 7 days to mark PRs as stale, is this too aggressive for this repo?
  For context, this repo has 53 open PRs. With this setting, 46 would be identified as stale.
• Should any PRs be exempt from stale?
  The specification repo exempts any PRs marked as release:after-ga. I don't see many PRs labeled here, but this is an option.
• Should Issues be reviewed for stale?
  Specification repo proposed 1 year but was unable to agree on a policy. If this is wanted, labels can be used to exempt specific issues.

For significant contributions please make sure you have completed the following items:

• Appropriate CHANGELOG.md updated for non-trivial changes
• Design discussion issue #
• Changes in public API reviewed

[codecov]

Codecov Report

Merging #2769 (aca1fa7) into main (aad309b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2769   +/-   ##
=======================================
  Coverage   83.75%   83.75%           
=======================================
  Files         251      251           
  Lines        8864     8864           
=======================================
  Hits         7424     7424           
  Misses       1440     1440           

[reyang]

LGTM 👍

[reyang]

Adding few coins:

• The specification repo is using 7 days to mark PRs as stale, is this too aggressive for this repo?

I think it's a fair number. If someone came back from vacation and decided to work on a stale PR, making it active again is like 0.01% of the total work.

• Should any PRs be exempt from stale?

I don't have a use case in mind at this moment.

• Should Issues be reviewed for stale?
  Specification repo proposed 1 year but was unable to agree on a policy. If this is wanted, lables can be used to exempt specific issues.

That's a hard topic and here are my thoughts - having a 3-year active issue without any activity/updates is no better than not showing it in the default query. So I would vote for putting a 1-year policy - and we could learn from it and get feedback, never too late to make adjustments.

BTW, it's "label" instead of "lable" 😸

[alanwest]

If someone came back from vacation and decided to work on a stale PR, making it active again is like 0.01% of the total work.

Coming back to work after vacation is the remaining 99.99%.