8295205: Add jcheck whitespace checking for markdown files

[magicus]

Markdown files are basically source code for documentation. It should have the same whitespace checks as all other source code, so we don't get spurious trailing whitespace changes.

---

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-8295205: Add jcheck whitespace checking for markdown files

Reviewers

• Erik Joelsson (@erikj79 - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 10671

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

Using diff file

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

[bridgekeeper]

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

@magicus The following labels will be automatically applied to this pull request:

• build
• client
• core-libs
• hotspot
• security

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (75cd1380)

[erikj79]

Thank you! Since I enabled visible whitespace in emacs (to be able to properly edit makefiles) editing any file where trailing whitespace isn't enforced makes my eyes bleed. :)

[openjdk]

@magicus 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:

8295205: Add jcheck whitespace checking for markdown files

Reviewed-by: erikj

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 5 new commits pushed to the master branch:

• cb62f1c: 8295218: New KeepAliveTest.java has invalid copyright notice
• 9cf6651: 8294238: ZGC: Move CLD claimed mark clearing
• adaff7d: 8294900: Refactor ZObjArrayAllocator
• 86ec158: 8291226: Create Test Cases to cover scenarios for JDK-8278067
• 94ec729: 8263044: jdk/jfr/jvm/TestDumpOnCrash.java timed out

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

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

[magicus]

/integrate

[openjdk]

Going to push as commit 8607842.
Since your change was applied there have been 5 commits pushed to the master branch:

• cb62f1c: 8295218: New KeepAliveTest.java has invalid copyright notice
• 9cf6651: 8294238: ZGC: Move CLD claimed mark clearing
• adaff7d: 8294900: Refactor ZObjArrayAllocator
• 86ec158: 8291226: Create Test Cases to cover scenarios for JDK-8278067
• 94ec729: 8263044: jdk/jfr/jvm/TestDumpOnCrash.java timed out

Your commit was automatically rebased without conflicts.

[openjdk]

@magicus Pushed as commit 8607842.

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