ci: Prevent CI workflow to be triggered during release #630
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull request overview
This PR prevents CI workflows from being triggered during the release process by adding [skip ci] to the release commit message. This ensures that the "on merge to main" workflow doesn't run when the version bump commit is pushed, avoiding unnecessary CI runs mid-release.
Changes:
- Updated the Maven SCM plugin commit message to include
[skip ci]directive
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
dgriffon
approved these changes
Feb 2, 2026
baptistegrimaud
deleted the
prevent-ci-workflow-to-be-triggered-during-release
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When bumping the
versionfield in thepackage.jsonas part of the release process, use[skip ci]in the commit message to ensure there is no workflow triggered when that commit is pushed to main.Similar to Jahia/user-password-authentication#136.
Tip
Documentation to guide the reviews: How to do a code review