lirantal/Automerge on Green Checks
Safely merge eligible pull requests after their visible checks and statuses are green.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | GitHub token used to read pull requests/checks/statuses and merge pull requests. | no | ${{ github.token }} |
| merge-method | Merge method to use. One of merge, squash, or rebase. | no | squash |
| label | Pull request label required for automerge when require-label is true. | no | automerge |
| require-label | Require the configured label before attempting to merge. | no | true |
| allow-forks | Allow merging pull requests whose head branch is from a fork. | no | false |
| green-observations-required | Number of consecutive green observations required before merging. | no | 4 |
| poll-interval-seconds | Seconds to wait between observations while checks are still pending. | no | 60 |
| timeout-seconds | Maximum seconds to wait for a stable green state before failing. | no | 3600 |
| ignored-check-names | Comma-separated check run names to ignore when deciding if the pull request is green. | no | automerge,Automerge |
Outputs
| name | description |
|---|---|
| merged | Whether the action merged the pull request. |
| reason | The merge or skip reason. |
| pull-request-number | Pull request number considered by the action. |
| head-sha | Pull request head SHA considered by the action. |
| merge-sha | SHA returned by GitHub when a pull request is merged. |