This action will manage triage state in issues.
Create a file named .github/workflows/triage.yml.
name: Triage
on:
issues:
types: [opened, closed, milestoned, demilestoned]
project_card:
types: [created, deleted]
jobs:
build:
name: Triage
runs-on: ubuntu-16.04
steps:
- uses: Logerfo/[email protected]
with:
github-token: ${{ secrets.GITHUB_TOKEN }}All values are default.
name: Triage
on:
issues:
types: [opened, closed, milestoned, demilestoned] # The last two are not needed if milestone is set to false
project_card: # Not needed if project is set to false
types: [created, deleted]
jobs:
build:
name: Triage
runs-on: ubuntu-16.04
steps:
- uses: Logerfo/[email protected]
with:
github-token: ${{ secrets.GITHUB_TOKEN }} # The `GITHUB_TOKEN` secret.
label: triage # The triage label of your repository.
project: true # Enable or disable the idea that adding an issue to a project drops its triage state.
milestone: true # Enable or disable the idea that setting a milestone to an issue drops its triage state.You can use (at your own risk) the release branch instead of the specific version tag.
Never user master, since the distribution file does not exist in this branch and the action will always fail.
The GitHub Projects API is currently in beta. This means that it can have a breaking change anytime, which may break this action and it might not be fixed.
Click here.
If you have suggestions for how close-label could be improved, or want to report a bug, open an issue! We'd love all and any contributions.
For more, check out the Contributing Guide.
BTC: 1LoGErFoNzE1gCA5fzk6A82nV6iJdKssSZ
