Renovate unique commit on updates #28624
Unanswered
ifalex
asked this question in
Request Help
Replies: 1 comment
-
Probably related to also this old question: renovatebot/config-help#520 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab
Please tell us more about your question or problem
When renovate is doing an update on a branch it never creates a new commit to the branch therefore automations regarding development versions can't be applied as you'll always fall under git tag existence.
Example:
We have a job to release development jobs based on conventional commits. The problem with the renovate behavior is that it is always having one commit per branch, therefore the semantic-release won't see any change, therefore not creating a new tag.
Is any configuration that can be added to modify this behavior? Any strategy?
Thanks for helping!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions