This repository has been archived by the owner on Oct 8, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 53
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Andy McKay
authored
Sep 20, 2019
1 parent
7e5f047
commit 42e28f9
Showing
1 changed file
with
19 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,20 @@ | ||
Labels issues when they land in a repo with the `needs-triage` label. | ||
Automatically labels issues, by adding new labels to the issue. You define the labels you'd like to add to your issues in the YAML file. | ||
|
||
This is probably going to get a bit more sophisticated to meet all our needs but will do for the moment. | ||
To add it to your workflow: | ||
|
||
``` | ||
- uses: andymckay/[email protected] | ||
with: | ||
repo-token: "${{ secrets.GITHUB_TOKEN }}" | ||
labels: "needs-triage, bug" | ||
``` | ||
|
||
This adds the `needs-triage` and `bug` issues to the issue. The most common approach is to do this when issues are created, you can do this with the following in your workflow file: | ||
|
||
``` | ||
on: | ||
issues: | ||
types: [opened] | ||
``` | ||
|
||
That's it. |