Workflows: Label stale issues and PRs, and issue triage labels

Adam Snyderrequested to merge
github/fork/armsnyder/workflow-stale into master

Description

Adds workflows for:

  • Marking issues and PRs as "stale" and then closing them after 2 weeks
  • Adding "needs-triage" and conditionally "bug" labels (based on a regex) for newly opened issues
  • Unmarking issues as "stale" or "waiting-response" whenever there is activity
  • Removing labels "waiting-response" or "needs-triage" if an issue is closed with those labels

Note that I configured the stale workflow to never close an issue with a "bug", "enhancement", or "keep-open" label.

I tested most of this in my fork, but I have not tested the cron job workflow. It is copied from the action documentation, so it should work.

PR Checklist

  • Resource attributes match 1:1 the names and structure of the API resource in the GitLab API documentation.
  • Examples are updated with:
    • A *.tf file for the resource/s with at least one usage example
    • A *.sh file for the resource/s with an import example (if applicable)
  • New resources have at minimum a basic test with three steps:
    • Create the resource
    • Update the attributes
    • Import the resource
  • No new //lintignore comments that came from copied code. Linter rules are meant to be enforced on new code.

Merge request reports