Switched to custom issue labeling bot

refs https://github.com/TryGhost/Toolbox/issues/81

- the existing `label-actions` tooling was deprecated and shut down but
  after reviewing, it wasn't expressive enough for our workflow use cases
- we wanted a tool we could drop into our repos and it works without
  extra configuration
- I've developed the `tryghost/label-actions` GitHub Action which will
  supports all our labeling flows for triaging
- this commit switches the repo over to using that
- configured the scheduled tasks to run at midnight daily
This commit is contained in:
Daniel Lockyer 2021-11-12 10:57:27 +00:00
parent 8714b4e2b7
commit bf4ae212fd
No known key found for this signature in database
GPG Key ID: D21186F0B47295AD
2 changed files with 13 additions and 22 deletions

View File

@ -1,22 +0,0 @@
# Configuration for Label Actions - https://github.com/dessant/label-actions
# Configuration settings just for issues
issues:
actions:
support-request:
comment: |
Hey @{issue-author} :wave: We ask that you please do not use GitHub for help or support 😄. We use GitHub solely for bug-tracking and on-going feature development.
Many questions can be answered by reviewing our [documentation](https://ghost.org/docs/). If you can't find an answer then our [forum](https://forum.ghost.org) is a great place to get community support, plus it helps create a central location for searching problems/solutions.
FYI: Many projects have their own support guidelines and GitHub will highlight them for you as it did here, or the project owners will use issue templates to point you in the right direction. Reading the guidelines or issue templates before opening issues can save you and project maintainers valuable time.
close: true
feature-request:
comment: |
Hey @{issue-author} :wave: Friendly reminder: we don't track feature requests on GitHub.
Please look for similar ideas to vote for on the [forum](https://forum.ghost.org/c/Ideas/l/votes) and if you can't anything similar then post your own idea.
FYI: Many projects have their own support guidelines and GitHub will highlight them for you as it did here, or the project owners will use issue templates to point you in the right direction. Reading the guidelines or issue templates before opening issues can save you and project maintainers valuable time.
close: true

13
.github/workflows/label-actions.yml vendored Normal file
View File

@ -0,0 +1,13 @@
name: 'Label Issues'
on:
issues:
types: [opened, labeled]
schedule:
- cron: '0 * * * *'
jobs:
action:
runs-on: ubuntu-latest
steps:
- uses: tryghost/label-actions@main