This action generates the changesets status in PRs, for example, whether it has changeset files and which packages will be released if the PR is merged.
It requires the repo to be checked out, and will automatically fetch the PR head ref into a temporary detached worktree in order to infer the changed files and packages.
- Needs repo checked out
- Job permissions: none
- Workflow triggers:
Caution
Do not run untrusted code when using the pull_request_target event.
pull_request_target can be useful to support PRs from forks, however it enables write permissions by default which can be a security risk if untrusted code is executed and the permissions aren't scoped down.
Tip
Check out the docs to learn how to set up commenting changesets status on PRs.
Inputs: none
| Outputs | Description |
|---|---|
comment-body |
The generated comment body to present the changesets status in PRs. |