You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,12 +13,14 @@ Usage:
13
13
Flags:
14
14
--config-path string A custom config path, relative to the repository root
15
15
--data string A JSON string of the 'event'type (issue event or pull request event)
16
+
--fields strings Fields to evaluate for labeling (title, body) (default [title,body])
16
17
-h, --help helpfor labeler
17
18
--id int The integer id of the issue or pull request
18
19
-o, --owner string GitHub Owner/Org name [GITHUB_ACTOR]
19
20
-r, --repo string GitHub Repo name [GITHUB_REPO]
20
21
-t, --type string The target event type to label (issues or pull_request) [GITHUB_EVENT_NAME]
21
22
-v, --version version for labeler
23
+
22
24
```
23
25
24
26
Example usage:
@@ -70,6 +72,8 @@ labels:
70
72
- '\bquestion\b'
71
73
```
72
74
75
+
Note that simple schema doesn't allow for some of the more advanced features of the full schema, such as excluding patterns or customizing comments for issues and pull requests. If you need those features, consider using the full schema.
76
+
73
77
### Full Schema
74
78
75
79
```yaml
@@ -81,6 +85,11 @@ enable:
81
85
prs: true
82
86
# comments object allows you to specify a different message for issues and prs
83
87
88
+
# (Optional): Determine which fields of the issue or pull request to evaluate.
0 commit comments