-
-
Notifications
You must be signed in to change notification settings - Fork 40
"Skip" out of range updates (e.g. comment, log entry) rather than failing the pipeline #423
Copy link
Copy link
Closed
Description
Prerequisites
- I have written a descriptive issue title
- I have searched existing issues to ensure the feature has not already been requested
🚀 Feature Proposal
Currently CI runs that are out of the configured semver range are marked as failed due to the core.setFailed call in https://github.com/fastify/github-action-merge-dependabot/blob/main/src/action.js#L80
I'd rather have an option to receive a log message or even PR comment that this PR is out of scope for auto merge and requires manual work.
Motivation
We try to use the GH setting: "only merge if all workflows succeeded" but with the current behavior that is not possible.
Also, the overall displayed status (via e.g. Refined GitHub) is adulterated because the update could be compatible (e.g. only ancient Node.js versions were dropped) but this action sets the CI pipeline to a red failure flag even though the normal pipeline passed just fine.
Example
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels