Highlight/indicate which PRs will automerge

[MPV]

Tell us more.

Could renovate show (without opening the PR) which PRs will be automerged?

For example in the:

• Onboarding PR (you will get these PRs AND they will automerge)
• Dependency Dashboard (when these PRs are created, they will be automerged)

For example, when onboarding many repositories using sharable presets that include some package rules which will trigger automerge, when developers get the onboarding PR it would be helpful if we/Renovate could help them understand which dependencies will be quickly rolled out (automerged) and which ones will need manual handling/review.

I've searched for similar requests, and the closest I've found is this one (which doesn't yet nail my specific need for it showing in the onboarding PR nor dependency dashboard, which labels wouldn't solve):

• Add a configured label to a PR if automerge is enabled for it #24662

[MPV]

Alternatives considered:

1. "Manual detection"
   While it could be manually added to each packageRule that contains automerge: true it would be tedious to maintain across repos/presets/developers.
2. "Indicate with labels"
   As they only show on the PRs (not before their creation, i.e. in onboarding PR or dependency dashboard) it's not as easy to understand that triggering this kind of PR will also be automatically merged.
3. "Indicate with commit prefix or suffix"
   As those are already used for other things (prefix for semantic commits, and suffix for other things) they might clash/overwrite other behaviour.

[MPV]

Maybe (as I guess rarkins may have elluded to in #24662?) we could have a templating field such as isAutomerging to allow this to be included in commit messages?

[MPV]

The expandable section for each dependency under "What to expect" in the onboarding PR is another place where it might be helpful to show whether a upcoming PR will be automerged (if not in the commit/PR title), i.e:

[rarkins]

I think this work is dependent on "Dependency Dashboard Templating", similar to how we allowed for prBody templating long ago. We can then progressively expose various parts of the dashboard strings for templating. Potentially changing defaults later too, if we like the ideas