Proper name for hgupdate-sync-label

[rwestberg]

Hi all,

Please review this minor change that updates the name of the sync label to the one actually in use.

Best regards,
Robin

---

Progress

• Change must not contain extraneous whitespace
• Change must be properly reviewed

Reviewers

• Erik Helin (@edvbld - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/skara pull/795/head:pull/795
$ git checkout pull/795

[bridgekeeper]

👋 Welcome back rwestberg! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@rwestberg The following labels will be automatically applied to this pull request: bots. When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label (add|remove) "label" command.

[edvbld]

Looks good!

[openjdk]

@rwestberg This change now passes all automated pre-integration checks. When the change also fulfills all project specific requirements, type /integrate in a new comment to proceed. After integration, the commit message will be:

Proper name for hgupdate-sync-label

Reviewed-by: ehelin

• If you would like to add a summary, use the /summary command.
• To credit additional contributors, use the /contributor command.
• To add additional solved issues, use the /issue command.

Since the source branch of this PR was last updated there have been 8 commits pushed to the master branch:

• 2830d50: 550: "branch has unmerged commits" message could be clarified by the bot
• 6a3e346: git-pr: git pr sponsor should sponsor
• ea08e68: git-pr-approve: allow configurable message
• 2e89e20: git-pr-fetch: remove --branch option
• 1377103: git-pr-checkout: better helptext
• 9b24968: git-pr-test: add flags --job and --approve
• fbac52c: git-pr: remove --no-commit from git apply
• ecbeb09: Include 'treconfigure' in help for git trees

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge master into your branch, and then specify the current head hash when integrating, like this: /integrate 2830d500e158669cdfcc9cd7398b6466a236c801.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (28bc999)

[rwestberg]

/integrate

[openjdk]

@rwestberg The following commits have been pushed to master since your change was applied:

• 2830d50: 550: "branch has unmerged commits" message could be clarified by the bot
• 6a3e346: git-pr: git pr sponsor should sponsor
• ea08e68: git-pr-approve: allow configurable message
• 2e89e20: git-pr-fetch: remove --branch option
• 1377103: git-pr-checkout: better helptext
• 9b24968: git-pr-test: add flags --job and --approve
• fbac52c: git-pr: remove --no-commit from git apply
• ecbeb09: Include 'treconfigure' in help for git trees

Your commit was automatically rebased without conflicts.

Pushed as commit ef99a66.