Git put - no fast forward #8649
Replies: 2 comments 1 reply
-
I've had success using the Here's an example resource configuration: - name: version
type: semver
icon: tag
source:
initial_version: "1.0.0"
driver: git
uri: <your-repo>
branch: version
file: version
private_key: <private key for github>
git_user: <your git user>
commit_message: "[ci skip] Update version to %version%" That way, it didn't cause any endless loops, since it didn't live on the Not sure if this solution is applicable, but I hope it helps! |
Beta Was this translation helpful? Give feedback.
-
Alternatively, if you rather keep the file in the same branch as the rest of the source code, you can create another You'd end up having 2 resources for your repo, but only 1 would actually trigger your pipeline. For the version-specific resource, you can add |
Beta Was this translation helpful? Give feedback.
-
Trying to look for a way to update a semver inside a file on a repo but without FF on the commit ID. bc if the commit ID changes, it triggers CI to run over and over in a loop. Has anyone been successful at doing non fast forward puts?
Beta Was this translation helpful? Give feedback.
All reactions