[MINOR] Add PR description validation on documentation updates

[yihua]

Change Logs

As above, to make PR description validation strict.

No information in the "Documentation Update" section in the PR description will trigger PR validation failure:

Impact

As above.

Risk level

none

Documentation Update

none

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[danny0405]

Hmm, most of the PRs does not need update for doc, is it reasonable to by default do all the validations? And the [MINOR] xxx style title seems been fixed to pass the validation right?

[yihua]

Hmm, most of the PRs does not need update for doc, is it reasonable to by default do all the validations? And the [MINOR] xxx style title seems been fixed to pass the validation right?

User needs to just add N/A to the "Documentation Update" section in the PR description in this case (i.e., what this PR does). This is a reminder for author to check if there is any documentation update needed, not necessary to do update if the code changes are not user-facing.

[yihua]

@danny0405 I updated the template to be more instructive so user knows to put "N/A" if no docs update is needed.

[danny0405]

+1, but I still think it is too strict for force update for the doc part.

[hudi-bot]

CI report:

• ca10086 Azure: CANCELED
• fb664ad UNKNOWN

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[yihua]

+1, but I still think it is too strict for force update for the doc part.

We can experiment with this. This will be a good reminder for people to think about docs. We still have features of which the docs is missing.

[yihua]

"Java CI / validate-source", "Update Pr Compliance / run-tests", and "validate pr / validate-pr" pass which are suffucient for the tooling changes. There is no change to the production code. Merging this now.