8333743: Change .jcheck/conf branches property to match valid branches

[kevinrushforth]

Update the branches property in .jcheck/conf to allow branches, now that we are using them for JDK stabilization. This will allow integrators to use Skara to create new stabilization branches (we had to do it manually this time).

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8333743: Change .jcheck/conf branches property to match valid branches (Bug - P2)

Reviewers

• Erik Joelsson (@erikj79 - Reviewer)
• Iris Clark (@irisclark - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19582/head:pull/19582
$ git checkout pull/19582

Update a local copy of the PR:
$ git checkout pull/19582
$ git pull https://git.openjdk.org/jdk.git pull/19582/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 19582

View PR using the GUI difftool:
$ git pr show -t 19582

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19582.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back kcr! 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]

@kevinrushforth This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8333743: Change .jcheck/conf branches property to match valid branches

Reviewed-by: erikj, iris

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@erikj79, @irisclark) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

@kevinrushforth The following label will be automatically applied to this pull request:

• build

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 pull request command.

[mlbridge]

Webrevs

• 00: Full (f3588b26)

[kevinrushforth]

/integrate

[openjdk]

@kevinrushforth
Your change (at version f3588b2) is now ready to be sponsored by a Committer.

[JesperIRL]

/sponsor

[openjdk]

Going to push as commit 2a37764.

[openjdk]

@JesperIRL @kevinrushforth Pushed as commit 2a37764.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.