auto-cherry-pick fixes

Author: rsill-neo4j

.github/workflows/auto-backport.yml

@@ -11,7 +11,6 @@ jobs:
       github.event.pull_request.merged == true
       && contains(github.event.pull_request.labels.*.name, 'cherry-pick')
       && github.event.action == 'closed'
-      )
     steps:
       - name: Cherry-pick action
         uses: sorenlouv/backport-github-action@929f69d04adbc196d982e60f02837b6cc00b3129

README.adoc

@@ -80,15 +80,15 @@ There are a few edge cases where we might want to work only on the current branc
 
 === Enable automatic cherry-picking on a PR
 
-To enable automatic cherry-picking on a PR, add the label `auto-cherry-pick` to it.
+To enable automatic cherry-picking on a PR, add the label `cherry-pick` to it.
 Without it, the responsible GitHub action is not going to be triggered.
 
-To select the target branches you would like to cherry-pick your PR to, add labels of the following structure: `auto-cherry-pick-to-<targetBranch>`.
-For example: `auto-cherry-pick-to-cypher-25` to cherry-pick it to the branch `cypher-25` or `auto-cherry-pick-to-5.x` for the branch `5.x`.
+To select the target branches you would like to cherry-pick your PR to, add labels of the following structure: `cherry-pick-to-<targetBranch>`.
+For example: `cherry-pick-to-cypher-25` to cherry-pick it to the branch `cypher-25` or `cherry-pick-to-5.x` for the branch `5.x`.
 You may even add new labels for branches that do not have such a label yet.
 
-The feature is triggered by either merging a PR with the `auto-cherry-pick` label or by adding the `auto-cherry-pick` label to an already closed and merged PR.
-In the latter case, ensure that you first add the labels containing the target branches and then finally the `auto-cherry-pick` label.
+The feature is triggered by either merging a PR with the `cherry-pick` label or by adding the `cherry-pick` label to an already closed and merged PR.
+In the latter case, ensure that you first add the labels containing the target branches and then finally the `cherry-pick` label.
 Otherwise the automation starts without any target branches.