step-security/StepSecurity Label Merge Conflicts
Detect pull requests with merge conflicts and label them. Optionally remove a separate label and post comments when a PR becomes dirty or clean again.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| repoToken | GitHub token used to read pull requests and mutate labels/comments. Typically secrets.GITHUB_TOKEN. | yes | — |
| dirtyLabel | Label to add to a pull request whose mergeable state is CONFLICTING. | yes | — |
| removeOnDirtyLabel | Label to remove from a pull request when it becomes dirty (e.g. 'ready to merge'). | no | — |
| retryAfter | Seconds to wait before re-checking pull requests whose mergeable state is UNKNOWN. | no | 120 |
| retryMax | Maximum number of retries when GitHub reports UNKNOWN mergeable state. | no | 5 |
| continueOnMissingPermissions | If true, log a warning and continue when the supplied token lacks permission to modify labels or comments. Useful for fork pull requests with a read-only token. | no | false |
| commentOnDirty | Markdown body for a comment posted the first time a pull request is marked dirty. | no | — |
| commentOnClean | Markdown body for a comment posted when a previously-dirty pull request becomes clean. | no | — |
Outputs
| name | description |
|---|---|
| prDirtyStatuses | JSON object mapping each pull request number to a boolean indicating whether it is currently dirty. |