|
| 1 | +--- |
| 2 | +name: List workflow runs for a repository |
| 3 | +example: octokit.actions.listWorkflowRunsForRepo({ owner, repo }) |
| 4 | +route: GET /repos/{owner}/{repo}/actions/runs |
| 5 | +scope: actions |
| 6 | +type: API method |
| 7 | +--- |
| 8 | + |
| 9 | +# List workflow runs for a repository |
| 10 | + |
| 11 | +Lists all workflow runs for a repository. You can use parameters to narrow the list of results. For more information about using parameters, see [Parameters](https://developer.github.com/v3/#parameters). |
| 12 | + |
| 13 | +Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `actions:read` permission to use this endpoint. |
| 14 | + |
| 15 | +```js |
| 16 | +octokit.actions.listWorkflowRunsForRepo({ |
| 17 | + owner, |
| 18 | + repo, |
| 19 | +}); |
| 20 | +``` |
| 21 | + |
| 22 | +## Parameters |
| 23 | + |
| 24 | +<table> |
| 25 | + <thead> |
| 26 | + <tr> |
| 27 | + <th>name</th> |
| 28 | + <th>required</th> |
| 29 | + <th>description</th> |
| 30 | + </tr> |
| 31 | + </thead> |
| 32 | + <tbody> |
| 33 | + <tr><td>owner</td><td>yes</td><td> |
| 34 | + |
| 35 | +</td></tr> |
| 36 | +<tr><td>repo</td><td>yes</td><td> |
| 37 | + |
| 38 | +</td></tr> |
| 39 | +<tr><td>actor</td><td>no</td><td> |
| 40 | + |
| 41 | +Returns someone's workflow runs. Use the login for the user who created the `push` associated with the check suite or workflow run. |
| 42 | + |
| 43 | +</td></tr> |
| 44 | +<tr><td>branch</td><td>no</td><td> |
| 45 | + |
| 46 | +Returns workflow runs associated with a branch. Use the name of the branch of the `push`. |
| 47 | + |
| 48 | +</td></tr> |
| 49 | +<tr><td>event</td><td>no</td><td> |
| 50 | + |
| 51 | +Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see "[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows)" in the GitHub Help documentation. |
| 52 | + |
| 53 | +</td></tr> |
| 54 | +<tr><td>status</td><td>no</td><td> |
| 55 | + |
| 56 | +Returns workflow runs associated with the check run `status` or `conclusion` you specify. For example, a conclusion can be `success` or a status can be `completed`. For more information, see the `status` and `conclusion` options available in "[Create a check run](https://developer.github.com/v3/checks/runs/#create-a-check-run)." |
| 57 | + |
| 58 | +</td></tr> |
| 59 | +<tr><td>per_page</td><td>no</td><td> |
| 60 | + |
| 61 | +Results per page (max 100) |
| 62 | + |
| 63 | +</td></tr> |
| 64 | +<tr><td>page</td><td>no</td><td> |
| 65 | + |
| 66 | +Page number of the results to fetch. |
| 67 | + |
| 68 | +</td></tr> |
| 69 | + </tbody> |
| 70 | +</table> |
| 71 | + |
| 72 | +See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository). |
0 commit comments