feat: support for fail-if-no-changes input

Currently if this action is used and no changes have been made to the
repository, the job will silently continue. This feature adds a new
flag `fail-if-no-changes`, which when enabled causes the job to fail
when there are no changes.
This commit is contained in:
Chris Buckley 2022-01-08 21:48:54 +00:00
parent dcd5fd746d
commit 171a10a802
7 changed files with 21 additions and 5 deletions

View file

@ -64,6 +64,7 @@ All inputs are **optional**. If not set, sensible defaults will be used.
| `team-reviewers` | A comma or newline-separated list of GitHub teams to request a review from. Note that a `repo` scoped [PAT](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) may be required. See [this issue](https://github.com/peter-evans/create-pull-request/issues/155). If using a GitHub App, refer to [Authenticating with GitHub App generated tokens](docs/concepts-guidelines.md#authenticating-with-github-app-generated-tokens) for the proper permissions. | |
| `milestone` | The number of the milestone to associate this pull request with. | |
| `draft` | Create a [draft pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests). | `false` |
| `fail-if-no-changes` | Whether the workflow should fail if a pull request wasn't created/updated. | `false` |
For self-hosted runners behind a corporate proxy set the `https_proxy` environment variable.
```yml