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
+4-27
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ Check out the _"EXAMPLE"_ issues and pull requests (open and closed) in this rep
10
10
11
11
---
12
12
Run specified actions or jobs for issue and PR comments through a `workflow.yaml` file:
13
+
13
14
```yaml
14
15
name: "Prow github actions"
15
16
on:
@@ -41,34 +42,8 @@ jobs:
41
42
github-token: "${{ secrets.GITHUB_TOKEN }}"
42
43
```
43
44
44
-
Automatically label PRs with the [Github actions/labeler](https://github.com/actions/labeler/blob/main/README.md) based on globs from `.github/labels.yml`:
45
-
```yaml
46
-
name: "Pull Request Labeler"
47
-
on:
48
-
- pull_request_target
49
-
50
-
jobs:
51
-
triage:
52
-
runs-on: ubuntu-latest
53
-
steps:
54
-
- uses: actions/labeler@main
55
-
with:
56
-
repo-token: "${{ secrets.GITHUB_TOKEN }}"
57
-
```
58
-
59
-
Your `.github/labels.yaml` may look like:
60
-
```yaml
61
-
# labels to be used with /area command
62
-
area:
63
-
- 'bug'
64
-
- 'important'
65
-
66
-
# File globs for PR labeler
67
-
tests:
68
-
- '**/*.test.ts'
69
-
```
70
-
71
45
You can automatically merge PRs based on a cron schedule if it contains the `lgtm` label:
46
+
72
47
```yaml
73
48
name: "Merge on lgtm label"
74
49
on:
@@ -89,6 +64,7 @@ jobs:
89
64
```
90
65
91
66
Prow Github actions also supports removing the lgtm label when a PR is updated
`/area [label1 label2 ...]` | anyone | adds an area/<> label(s) if it's defined in [the `.github/labels.yaml` file](./labeling.md)
21
-
`/kind [label1 label2 ...]` | anyone | adds a kind/<> label(s) if it's defined in [the `.github/labels.yaml` file](./labeling.md)
20
+
`/area [label1 label2 ...]` | anyone | adds an area/<> label(s) if it's defined in [the `.prowlabels.yaml` file](./labeling.md)
21
+
`/kind [label1 label2 ...]` | anyone | adds a kind/<> label(s) if it's defined in [the `.prowlabels.yaml` file](./labeling.md)
22
22
`/lgtm` | [OWNERS](#owners) if present, otherwise Collaborators and Org Members | adds the `lgtm` label. This is used for [automatic PR merging]()
23
23
`/lgtm cancel` | [OWNERS](#owners) if present, otherwise Collaborators and Org Members | removes the `lgtm` label
24
24
`/hold` | anyone | adds the `hold` label which prevents [automatic PR merging](./automatic-merging.md). Also see [lgtm removal on pr update](./pr-jobs.md)
25
25
`/hold cancel` | anyone | removes the `hold` label
26
-
`/priority [label1 label2 ...]` | anyone | adds a priority/<> label(s) if it's defined in [the `.github/labels.yaml` file](./automatic-merging.md)
26
+
`/priority [label1 label2 ...]` | anyone | adds a priority/<> label(s) if it's defined in [the `.prowlabels.yaml` file](./automatic-merging.md)
27
27
`/remove [label1 label2 ...]` | Collaborators | removes a specified label(s) on an issue / PR
Copy file name to clipboardExpand all lines: docs/cron-jobs.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,13 @@ The following jobs are supported through [cron Github workflows]().
5
5
Jobs | Description
6
6
--- | ---
7
7
`lgtm` | Will attempt to automatically merge a PR with the `lgtm` label. Blocked by the `hold` label. Removed by the [lgtm PR job on pr update](./pr-jobs.md)
8
-
`pr-labeler` | Labels PRs with labels based on file globs found in `.github/labels.yaml`. See [docs on PR labeler for more info](pr-labeling.md)
8
+
`pr-labeler` | **(DEPRECATED)**Labels PRs with labels based on file globs found in `.github/labels.yaml`. See [docs on PR labeler for more info](pr-labeling.md)
9
9
10
-
## PR labeler
11
-
> What is this Chron job PR labeler?
10
+
> What is the Chron job PR labeler?
12
11
13
12
This job is a legacy feature of Github Prow bot which would label PRs
14
13
based on a chron schedule. This was created since Github at the time did not provide a way
15
-
to securely run actions (and therefore code) from PR forks, which could possibly be untrusted.
14
+
to securely run actions (and therefore code) from PR forks, which could possibly be untrusted.
16
15
This chron job runs from _the main branch_ and not forks, therefore preventing any
17
16
forked malicious code from being run against the repository.
18
17
@@ -36,6 +35,7 @@ However, this has some known limitations. The chron labeler queries Github in 10
36
35
This can trigger github to rate limit the bot.
37
36
38
37
This job may be run with the following workflow configuration:
0 commit comments