Change commit message and PR title to imperative mood

[andrross]

Because I'm a pedant.

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[saratvemulapalli]

Glad you did this on a Friday 😃

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10614/
• CommitID: 9c7cb9d
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/10622/
• CommitID: 9c7cb9d

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-6177-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 61304a6a31cc2a0f722a867f515e5cb68d9050d6
# Push it to GitHub
git push --set-upstream origin backport/backport-6177-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-6177-to-2.x.

[dblock]

Is it "Increment" or "Increments"?

[andrross]

Is it "Increment" or "Increments"?

"Increment", per the guidance here: https://cbea.ms/git-commit/

The way I remember this is by referring to how git itself formulates messages for things like git revert:

Revert "Andrew's idea that seemed great at the time"

This reverts commit abcd1234

[dblock]

@andrross I think I am thrown off by dependapot which keeps saying "bumps". We should fix it probably.

[andrross]

@dblock dangoslen/dependabot-changelog-helper#131