Does Renovate revert PR titles that have had manual edits?

[Ali-Haider-24]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

43.185.1

Please tell us more about your question or problem

Is the Renovate bot supposed to revert PR titles if the PR titles have been manually modified?

We have these settings in our renovate.json file:

 "commitMessageAction": "Update", 
 "commitMessageTopic": "{{depName}}",
 "commitMessageExtra": "from {{currentVersion}} to {{newVersion}}",

and we have a package rule that modifies the commitMessageTopic if the dependency starts with drupal/:

 "packageRules": [
    {
      "commitMessageTopic": "{{depName}} module",
      "matchPackageNames": [
        "/^drupal//"
      ]
    },

So our PR titles end up looking like: "Update drupal/somemodule module from 1.0.0 to 2.0.0"

However, our team adds ticket references at the start of the PR title. So the PR title becomes: "[Ticket-1234] Update drupal/somemodule module from 1.0.0 to 2.0.0"

It seems like the Renovate bot picks up on this and reverts the PR title to the original by removing the ticket reference.

Is this normal behaviour for the Renovate bot? Is there some configuration setting that tells the bot to not change PR titles if they have been manually edited?

Logs (if relevant)

Logs

DEBUG: Found existing PR (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop"
}

DEBUG: PR cache matches but it has been edited in the past 24hrs, so processing PR (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop"
}

DEBUG: Fetching changelog: https://git.drupalcode.org/project/book.git (3.0.1 -> 3.0.4) (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop"
}

INFO: Unknown platform, skipping changelog fetching. (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop",
  "sourceUrl": "https://git.drupalcode.org/project/book.git",
  "hostType": null
}

DEBUG: Processing existing PR (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop"
}

DEBUG: PR title changed (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop",
  "branchName": "renovate/drupal-book-3.x",
  "oldPrTitle": " [GOVCMSD11-605] Update drupal/book module from 3.0.1 to 3.0.4",
  "newPrTitle": "Update drupal/book module from 3.0.1 to 3.0.4"
}

DEBUG: updatePr(1921, Update drupal/book module from 3.0.1 to 3.0.4, body) (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop"
}

DEBUG: PR updated...prNo: 1921 (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop"
}

INFO: PR updated (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop",
  "pr": 1921,
  "prTitle": "Update drupal/book module from 3.0.1 to 3.0.4"
}

DEBUG: setPrCache() (branch="renovate/drupal-book-3.x")
{
  "baseBranch": "4.x-develop"
}

[RahulGautamSingh]

Yes, this is expected behavior, with no workaround currently.

You could create a commit along with PR title change, bot will detect external commit and stop updating the PR.

[Ali-Haider-24]

For clarity, in what conditions will the bot revert the PR titles? I've seen some inconsistent behaviour where I manually run a Renovate scan of a repository, and the bot does not revert a modified PR title (and the PR had no extra commits).

Does it only revert the PR title if a PR is rebased or if the PR itself is updated (like a new version of the dependency is released)?

[RahulGautamSingh]

The inconsistent behavior is also expected, as Renovate stops updating pr titles after they have not been updated by the bot for 24 hours.