lockfile maintenance PR titles inconsistently including groupName

[andrewpollock]

How are you running Renovate?

A Mend.io-hosted app

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

https://github.com/google/osv.dev/blob/master/renovate.json is our config and we have a series of groups to chunk the scope of the PRs generated.

We're seeing the groupName be inconsistently reflected in the PR titles:

REPO            ID     TITLE                                     LABELS        UPDATED             
google/osv.dev  #2833  chore(deps): lock file maintenance group  dependencies  about 1 day ago
google/osv.dev  #2832  chore(deps): lock file maintenance group  dependencies  about 1 day ago
google/osv.dev  #2831  chore(deps): lock file maintenance tools  dependencies  about 44 minutes ago
google/osv.dev  #2830  chore(deps): lock file maintenance group  dependencies  about 12 hours ago
google/osv.dev  #2829  chore(deps): lock file maintenance group  dependencies  about 12 hours ago
google/osv.dev  #2828  chore(deps): lock file maintenance group  dependencies  about 12 hours ago
google/osv.dev  #2825  fix(deps): update indexer                 dependencies  about 44 minutes ago

Additionally, looking at google/osv.dev#714,

and the console at https://developer.mend.io/github/google/osv.dev

it looks like something isn't being correctly inferred from... somewhere?

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[andrewpollock]

/cc @another-rex

[RahulGautamSingh]

1. Using commitMessageAction as noted in the docs is a risky thing. (compilicates the logic sometimes)
2. Both groupName and commitMessageAction are trying to modify the same thing ie. prTitle & commitMessage.

So, the issue could be occuring when we apply the package rules, or it could be where prTitle / commitMessage are computed.

I would recommend you go through the logic moving forwards from lookup stage to the update stage (where we create PRs) and debug it, cause that's the only way to figure it out.

We could help debug after you have some findings. (also, create a minimal reproduction it will help someone who might be interested in debugging this issue)

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team