upgrades
and prBodyDefinitions
access in templates
#29546
Unanswered
amezin
asked this question in
Request Help
Replies: 2 comments 5 replies
-
Is unavailability of |
Beta Was this translation helpful? Give feedback.
3 replies
-
It sounds like the better solution here would be that commitMessagePrefix is calculated "lazily" based on the branch data and not based on the "eager" calculation which is done today per-upgrade |
Beta Was this translation helpful? Give feedback.
2 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.
Bitbucket Server, Docker image ghcr.io/renovatebot/renovate:37.388.1-full
Please tell us more about your question or problem
This is likely two separate issues, but initially I'll start it as one discussion because of the context.
So, I have a config preset, where dependencies are associated with Jira issues using
packageRules
andprBodyDefinitions
.Because of how Bitbucket Server <-> Jira integration works, issues need to be referenced in the pull request title and commit message to link with the PR and commit. I can't simply use
commitMessagePrefix
, because updates can be grouped - so they should have multiple issue references, all in the commit message and PR title, andcommitMessagePrefix
isn't "mergeable".But if I try to use this:
"commitMessagePrefix": "{{#each upgrades}}{{{prBodyDefinitions.Issue}}} {{/each}}"
in group configuration, I get an empty prefix.It seems that
upgrades
aren't available in the commit message/PR title at all, because"commitMessageTopic": "{{#each upgrades}}{{depName}} {{/each}}"
also gives an empty topic.And
prBodyDefinitions
give no result even in PR description body:"prHeader": "Issues: {{#each upgrades}}{{{prBodyDefinitions.Issue}}} {{/each}}"
gives justIssues:
.upgrades
, however, are available in PR description:"prHeader": "depNames: {{#each upgrades}}{{{depName}}} {{/each}}"
works as I expected.But I need both
upgrades
andprBodyDefinitions
incommitMessagePrefix
template. Can these limitations be removed?Reproduction: https://github.com/amezin/renovate-template-issues
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions