diff --git a/docs/commit-message-check.md b/docs/commit-message-check.md
index bc4c9c3..8c2f572 100644
--- a/docs/commit-message-check.md
+++ b/docs/commit-message-check.md
@@ -4,24 +4,10 @@
 
 `eslint-github-bot`'s commit message check ensures that all pull requests which get merged into `main` have a valid commit message, based on [ESLint's commit message guidelines](https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes).
 
-The ESLint team uses GitHub's "Squash and Merge" feature to merge pull requests. When using this feature, the default commit message for the squashed commit is determined as follows:
-
-* If the pull request contains exactly one commit, that commit message is also used as the merge commit message.
-* If the pull request contains more than one commit, the title of the pull request is used as the merge commit message.
-
-To minimize the risk of an incorrect commit message getting merged into `main`, `eslint-github-bot` uses the same logic when evaluating a pull request; it checks the *commit message* if a pull request contains exactly one commit, and it checks the *title* if a pull request contains more than one commit.
+The ESLint team uses GitHub's "Squash and Merge" feature to merge pull requests. When using this feature, the default commit message for the squashed commit is the title of the pull request. To minimize the risk of an incorrect commit message getting merged into `main`, `eslint-github-bot` checks the title.
 
 ## How do I fix it?
 
-If this status check is failing on your pull request, you should first check what message the bot is referring to, by looking at the description next to the status check.
-
-* If the description says "*Commit message* doesn't follow guidelines", you should amend your commit message from the command line to conform to [ESLint's commit message guidelines](https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes). (This description will be used if your pull request has exactly one commit.)
-
-    ```bash
-    git commit --amend
-    git push --force
-    ```
-
-* If the description says "*PR title* doesn't follow commit message guidelines", you should fix your pull request title on github.com to conform to [ESLint's commit message guidelines](https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes). (This description will be used if your pull request has more than one commit.)
+If this status check is failing on your pull request, you should fix your pull request title on github.com to conform to [ESLint's commit message guidelines](https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes).
 
-    ![](./edit-pr-title-explanation.png)
+![](./edit-pr-title-explanation.png)
diff --git a/src/plugins/commit-message/createMessage.js b/src/plugins/commit-message/createMessage.js
index 0573469..d434195 100644
--- a/src/plugins/commit-message/createMessage.js
+++ b/src/plugins/commit-message/createMessage.js
@@ -17,12 +17,11 @@ const ERROR_MESSAGES = {
 /**
  * Create a comment message body with the error details
  * @param {Array<string>} errors list of the error codes
- * @param {boolean} isTitle whether it is for title or the commit message
  * @param {string} username username of the PR author
  * @returns {string} the message to comment
  * @private
  */
-module.exports = function commentMessage(errors, isTitle, username) {
+module.exports = function commentMessage(errors, username) {
     const errorMessages = [];
 
     errors.forEach(err => {
@@ -33,11 +32,11 @@ module.exports = function commentMessage(errors, isTitle, username) {
 
     return `Hi @${username}!, thanks for the Pull Request
 
-The **${isTitle ? "pull request title" : "first commit message"}** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 ${errorMessages.join("\n")}
 
-**To Fix:** You can fix this problem by ${isTitle ? "clicking 'Edit' next to the pull request title at the top of this page." : "running `git commit --amend`, editing your commit message, and then running `git push -f` to update this pull request."}
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 `;
diff --git a/src/plugins/commit-message/index.js b/src/plugins/commit-message/index.js
index a68b8c9..0015e63 100644
--- a/src/plugins/commit-message/index.js
+++ b/src/plugins/commit-message/index.js
@@ -10,7 +10,6 @@
 // Requirements
 //-----------------------------------------------------------------------------
 
-const { getCommitMessageForPR } = require("../utils");
 const commentMessage = require("./createMessage");
 const { TAG_LABELS } = require("./util");
 
@@ -104,16 +103,14 @@ async function processCommitMessage(context) {
     }
 
     const allCommits = await github.pullRequests.listCommits(context.issue());
-    const messageToCheck = getCommitMessageForPR(allCommits.data, payload.pull_request);
+    const messageToCheck = payload.pull_request.title;
     const errors = getCommitMessageErrors(messageToCheck);
     let description;
     let state;
 
     if (errors.length === 0) {
         state = "success";
-        description = allCommits.data.length === 1
-            ? "Commit message follows guidelines"
-            : "PR title follows commit message guidelines";
+        description = "PR title follows commit message guidelines";
 
         const labels = getCommitMessageLabels(messageToCheck);
 
@@ -123,12 +120,10 @@ async function processCommitMessage(context) {
 
     } else {
         state = "failure";
-        description = allCommits.data.length === 1
-            ? "Commit message doesn't follow guidelines"
-            : "PR title doesn't follow commit message guidelines";
+        description = "PR title doesn't follow commit message guidelines";
     }
 
-    // only check first commit message
+    // create status on the last commit
     await github.repos.createStatus(
         context.repo({
             sha: allCommits.data[allCommits.data.length - 1].sha,
@@ -141,7 +136,7 @@ async function processCommitMessage(context) {
 
     if (state === "failure") {
         await github.issues.createComment(context.issue({
-            body: commentMessage(errors, allCommits.data.length !== 1, payload.pull_request.user.login)
+            body: commentMessage(errors, payload.pull_request.user.login)
         }));
     }
 
diff --git a/src/plugins/release-monitor/index.js b/src/plugins/release-monitor/index.js
index 11fe84b..b8db1b5 100644
--- a/src/plugins/release-monitor/index.js
+++ b/src/plugins/release-monitor/index.js
@@ -5,8 +5,6 @@
 
 "use strict";
 
-const { getCommitMessageForPR } = require("../utils");
-
 const PATCH_COMMIT_MESSAGE_REGEX = /^(?:Build|Chore|Docs|Fix|Upgrade):/u;
 const POST_RELEASE_LABEL = "patch release pending";
 const RELEASE_LABEL = "release";
@@ -112,7 +110,7 @@ async function createAppropriateStatusForPR({ context, pr, pendingReleaseIssueUr
             state: "success",
             description: "No patch release is pending"
         });
-    } else if (isMessageValidForPatchRelease(getCommitMessageForPR(allCommits, pr))) {
+    } else if (isMessageValidForPatchRelease(pr.title)) {
         await createStatusOnPR({
             context,
             sha,
diff --git a/src/plugins/utils.js b/src/plugins/utils.js
deleted file mode 100644
index df54983..0000000
--- a/src/plugins/utils.js
+++ /dev/null
@@ -1,22 +0,0 @@
-/**
- * @fileoverview Utilities shared across multiple plugins.
- * @author Kevin Partington
- */
-
-"use strict";
-
-/**
- * Get the correct commit message for a PR
- * @param {Object[]} allCommits A list of commit objects from GitHub's API
- * @param {Object} pr Pull request object
- * @returns {string} Commit message
- */
-function getCommitMessageForPR(allCommits, pr) {
-    return allCommits.length === 1
-        ? allCommits[0].commit.message
-        : pr.title;
-}
-
-module.exports = {
-    getCommitMessageForPR
-};
diff --git a/tests/plugins/commit-message/__snapshots__/index.js.snap b/tests/plugins/commit-message/__snapshots__/index.js.snap
index ef61efa..bdd7672 100644
--- a/tests/plugins/commit-message/__snapshots__/index.js.snap
+++ b/tests/plugins/commit-message/__snapshots__/index.js.snap
@@ -1,9 +1,37 @@
 // Jest Snapshot v1, https://goo.gl/fbAQLP
 
+exports[`commit-message pull request edited Posts failure status if PR title is not correct 1`] = `
+"Hi @user-a!, thanks for the Pull Request
+
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
+
+- The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
+
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
+
+Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
+"
+`;
+
+exports[`commit-message pull request edited Posts failure status if PR title is not correct even when the first commit message is correct 1`] = `
+"Hi @user-a!, thanks for the Pull Request
+
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
+
+- The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
+
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
+
+Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
+"
+`;
+
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -18,7 +46,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -33,7 +61,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -48,7 +76,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -63,7 +91,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -78,7 +106,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -93,7 +121,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -108,7 +136,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -123,7 +151,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -137,7 +165,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -151,7 +179,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request edited Posts failure status if PR with multiple commits has invalid tag prefix in the title: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 
@@ -161,198 +189,211 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if commit message is not correct 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
+- The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: " New: " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: ": " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "Foo: " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "New " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "New : " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "New:" 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "Neww: " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "Revert: " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
-- The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "feat" 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "nNew: " 1`] = `
+exports[`commit-message pull request edited Posts failure status if the PR title has invalid tag prefix: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
-- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
+
+Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
+"
+`;
+
+exports[`commit-message pull request edited Posts failure status if the PR title is longer than 72 chars and don't set labels 1`] = `
+"Hi @user-a!, thanks for the Pull Request
+
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
+
+- The length of the commit message must be less than or equal to 72
+
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message has invalid tag prefix: "new: " 1`] = `
+exports[`commit-message pull request edited Posts failure status if there are multiple commit messages and the title is invalid 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if the commit message is longer than 72 chars and don't set labels 1`] = `
+exports[`commit-message pull request edited Posts failure status if there are multiple commit messages and the title is too long 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The length of the commit message must be less than or equal to 72
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if there are multiple commit messages and the title is invalid 1`] = `
+exports[`commit-message pull request opened Posts failure status if PR title is not correct 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -363,12 +404,13 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 "
 `;
 
-exports[`commit-message pull request edited Posts failure status if there are multiple commit messages and the title is too long 1`] = `
+exports[`commit-message pull request opened Posts failure status if PR title is not correct even when the first commit message is correct 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
-- The length of the commit message must be less than or equal to 72
+- The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
 **To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
@@ -379,7 +421,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -394,7 +436,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -409,7 +451,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -424,7 +466,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -439,7 +481,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -454,7 +496,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -469,7 +511,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -484,7 +526,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -499,7 +541,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -513,7 +555,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -527,7 +569,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request opened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 
@@ -537,198 +579,211 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if commit message is not correct 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
+- The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: " New: " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: ": " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "Foo: " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "New " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "New : " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "New:" 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "Neww: " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "Revert: " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
-- The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "feat" 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "nNew: " 1`] = `
+exports[`commit-message pull request opened Posts failure status if the PR title has invalid tag prefix: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
-- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
+
+Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
+"
+`;
+
+exports[`commit-message pull request opened Posts failure status if the PR title is longer than 72 chars and don't set labels 1`] = `
+"Hi @user-a!, thanks for the Pull Request
+
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
+
+- The length of the commit message must be less than or equal to 72
+
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message has invalid tag prefix: "new: " 1`] = `
+exports[`commit-message pull request opened Posts failure status if there are multiple commit messages and the title is invalid 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if the commit message is longer than 72 chars and don't set labels 1`] = `
+exports[`commit-message pull request opened Posts failure status if there are multiple commit messages and the title is too long 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The length of the commit message must be less than or equal to 72
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if there are multiple commit messages and the title is invalid 1`] = `
+exports[`commit-message pull request reopened Posts failure status if PR title is not correct 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -739,12 +794,13 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 "
 `;
 
-exports[`commit-message pull request opened Posts failure status if there are multiple commit messages and the title is too long 1`] = `
+exports[`commit-message pull request reopened Posts failure status if PR title is not correct even when the first commit message is correct 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
-- The length of the commit message must be less than or equal to 72
+- The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
 **To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
@@ -755,7 +811,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -770,7 +826,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -785,7 +841,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -800,7 +856,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -815,7 +871,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -830,7 +886,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -845,7 +901,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -860,7 +916,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -875,7 +931,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -889,7 +945,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -903,7 +959,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request reopened Posts failure status if PR with multiple commits has invalid tag prefix in the title: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 
@@ -913,198 +969,211 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if commit message is not correct 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
+- The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: " New: " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: ": " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "Foo: " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "New " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "New : " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "New:" 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "Neww: " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "Revert: " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
-- The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "feat" 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "nNew: " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if the PR title has invalid tag prefix: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
-- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
+
+Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
+"
+`;
+
+exports[`commit-message pull request reopened Posts failure status if the PR title is longer than 72 chars and don't set labels 1`] = `
+"Hi @user-a!, thanks for the Pull Request
+
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
+
+- The length of the commit message must be less than or equal to 72
+
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message has invalid tag prefix: "new: " 1`] = `
+exports[`commit-message pull request reopened Posts failure status if there are multiple commit messages and the title is invalid 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if the commit message is longer than 72 chars and don't set labels 1`] = `
+exports[`commit-message pull request reopened Posts failure status if there are multiple commit messages and the title is too long 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The length of the commit message must be less than or equal to 72
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if there are multiple commit messages and the title is invalid 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if PR title is not correct 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1115,12 +1184,13 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 "
 `;
 
-exports[`commit-message pull request reopened Posts failure status if there are multiple commit messages and the title is too long 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if PR title is not correct even when the first commit message is correct 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
-- The length of the commit message must be less than or equal to 72
+- The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
+- There should be a space following the initial tag and colon, for example 'feat: Message'.
 
 **To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
@@ -1131,7 +1201,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1146,7 +1216,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1161,7 +1231,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1176,7 +1246,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1191,7 +1261,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1206,7 +1276,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1221,7 +1291,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1236,7 +1306,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1251,7 +1321,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1265,7 +1335,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1279,7 +1349,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if PR with multiple commits has invalid tag prefix in the title: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 
@@ -1289,189 +1359,175 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if commit message is not correct 1`] = `
-"Hi @user-a!, thanks for the Pull Request
-
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
-
-- The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
-- There should be a space following the initial tag and colon, for example 'feat: Message'.
-
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
-
-Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
-"
-`;
-
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: " New: " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: " New: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: ": " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: ": " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "Foo: " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "Foo: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "New " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "New " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "New : " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "New : " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "New:" 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "New:" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "Neww: " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "Neww: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "Revert: " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "Revert: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 - The first letter of the tag should be in lowercase
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "feat" 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "feat" 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "nNew: " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "nNew: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message has invalid tag prefix: "new: " 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title has invalid tag prefix: "new: " 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
 `;
 
-exports[`commit-message pull request synchronize Posts failure status if the commit message is longer than 72 chars and don't set labels 1`] = `
+exports[`commit-message pull request synchronize Posts failure status if the PR title is longer than 72 chars and don't set labels 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **first commit message** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The length of the commit message must be less than or equal to 72
 
-**To Fix:** You can fix this problem by running \`git commit --amend\`, editing your commit message, and then running \`git push -f\` to update this pull request.
+**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
 
 Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
 "
@@ -1480,7 +1536,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if there are multiple commit messages and the title is invalid 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The commit message tag wasn't recognized. Did you mean \\"docs\\", \\"fix\\", or \\"feat\\"?
 - There should be a space following the initial tag and colon, for example 'feat: Message'.
@@ -1494,7 +1550,7 @@ Read more about contributing to ESLint [here](https://eslint.org/docs/developer-
 exports[`commit-message pull request synchronize Posts failure status if there are multiple commit messages and the title is too long 1`] = `
 "Hi @user-a!, thanks for the Pull Request
 
-The **pull request title** isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
+The **pull request title** isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.
 
 - The length of the commit message must be less than or equal to 72
 
diff --git a/tests/plugins/commit-message/index.js b/tests/plugins/commit-message/index.js
index 59331b8..d0f2b65 100644
--- a/tests/plugins/commit-message/index.js
+++ b/tests/plugins/commit-message/index.js
@@ -118,7 +118,7 @@ describe("commit-message", () => {
 
     ["opened", "reopened", "synchronize", "edited"].forEach(action => {
         describe(`pull request ${action}`, () => {
-            test("Posts failure status if commit message is not correct", async () => {
+            test("Posts failure status if PR title is not correct", async () => {
                 mockSingleCommitWithMessage("non standard commit message");
 
                 const nockScope = nock("https://api.github.com")
@@ -132,37 +132,104 @@ describe("commit-message", () => {
                     })
                     .reply(200);
 
-                await emitBotEvent(bot, { action });
+                await emitBotEvent(bot, {
+                    action,
+                    pull_request: {
+                        number: 1,
+                        title: "non standard commit message",
+                        user: { login: "user-a" }
+                    }
+                });
                 expect(nockScope.isDone()).toBeTruthy();
                 expect(nockScope2.isDone()).toBeTruthy();
             });
 
-            test("Posts success status if commit message is correct", async () => {
+            test("Posts failure status if PR title is not correct even when the first commit message is correct", async () => {
                 mockSingleCommitWithMessage("feat: standard commit message");
+
+                const nockScope = nock("https://api.github.com")
+                    .post("/repos/test/repo-test/statuses/first-sha", req => req.state === "failure")
+                    .reply(201);
+
+                const nockScope2 = nock("https://api.github.com")
+                    .post("/repos/test/repo-test/issues/1/comments", req => {
+                        expect(req.body).toMatchSnapshot();
+                        return true;
+                    })
+                    .reply(200);
+
+                await emitBotEvent(bot, {
+                    action,
+                    pull_request: {
+                        number: 1,
+                        title: "non standard commit message",
+                        user: { login: "user-a" }
+                    }
+                });
+                expect(nockScope.isDone()).toBeTruthy();
+                expect(nockScope2.isDone()).toBeTruthy();
+            });
+
+            test("Posts success status if PR title is correct", async () => {
+                mockSingleCommitWithMessage("feat: standard commit message");
+                const labelsScope = mockLabels(["feature"]);
+
+                const nockScope = nock("https://api.github.com")
+                    .post("/repos/test/repo-test/statuses/first-sha", req => req.state === "success")
+                    .reply(201);
+
+                await emitBotEvent(bot, {
+                    action,
+                    pull_request: {
+                        number: 1,
+                        title: "feat: standard commit message",
+                        user: { login: "user-a" }
+                    }
+                });
+                expect(nockScope.isDone()).toBeTruthy();
+                expect(labelsScope.isDone()).toBeTruthy();
+            });
+
+            test("Posts success status if PR title is correct even when the first commit message is not correct", async () => {
+                mockSingleCommitWithMessage("non standard commit message");
                 const labelsScope = mockLabels(["feature"]);
 
                 const nockScope = nock("https://api.github.com")
                     .post("/repos/test/repo-test/statuses/first-sha", req => req.state === "success")
                     .reply(201);
 
-                await emitBotEvent(bot, { action });
+                await emitBotEvent(bot, {
+                    action,
+                    pull_request: {
+                        number: 1,
+                        title: "feat: standard commit message",
+                        user: { login: "user-a" }
+                    }
+                });
                 expect(nockScope.isDone()).toBeTruthy();
                 expect(labelsScope.isDone()).toBeTruthy();
             });
 
-            test("Posts success status if commit message beginning with `Revert`", async () => {
+            test("Posts success status if PR title begins with `Revert`", async () => {
                 mockSingleCommitWithMessage("Revert \"chore: add test for commit tag Revert\"");
 
                 const nockScope = nock("https://api.github.com")
                     .post("/repos/test/repo-test/statuses/first-sha", req => req.state === "success")
                     .reply(201);
 
-                await emitBotEvent(bot, { action });
+                await emitBotEvent(bot, {
+                    action,
+                    pull_request: {
+                        number: 1,
+                        title: "Revert \"chore: add test for commit tag Revert\"",
+                        user: { login: "user-a" }
+                    }
+                });
                 expect(nockScope.isDone()).toBeTruthy();
             });
 
-            test("Posts failure status if the commit message is longer than 72 chars and don't set labels", async () => {
-                mockSingleCommitWithMessage("feat!: standard commit message very very very long message and its beond 72");
+            test("Posts failure status if the PR title is longer than 72 chars and don't set labels", async () => {
+                mockSingleCommitWithMessage("feat!: standard commit message very very very long message and its beyond 72");
 
                 const labelsScope = mockLabels(["feature", "breaking"]);
                 const nockScope = nock("https://api.github.com")
@@ -176,28 +243,19 @@ describe("commit-message", () => {
                     })
                     .reply(200);
 
-                await emitBotEvent(bot, { action });
+                await emitBotEvent(bot, {
+                    action,
+                    pull_request: {
+                        number: 1,
+                        title: "feat!: standard commit message very very very long message and its beyond 72",
+                        user: { login: "user-a" }
+                    }
+                });
                 expect(nockScope.isDone()).toBeTruthy();
                 expect(nockScope2.isDone()).toBeTruthy();
                 expect(labelsScope.isDone()).toBeFalsy();
             });
 
-            test("Posts success status if the commit message is longer than 72 chars after the newline", async () => {
-                mockSingleCommitWithMessage(
-                    `fix: foo\n\n${"A".repeat(72)}`
-                );
-
-                const labelsScope = mockLabels(["bug"]);
-
-                const nockScope = nock("https://api.github.com")
-                    .post("/repos/test/repo-test/statuses/first-sha", req => req.state === "success")
-                    .reply(201);
-
-                await emitBotEvent(bot, { action });
-                expect(nockScope.isDone()).toBeTruthy();
-                expect(labelsScope.isDone()).toBeTruthy();
-            });
-
             test("Posts success status if there are multiple commit messages and the title is valid", async () => {
                 mockMultipleCommits();
 
@@ -266,7 +324,7 @@ describe("commit-message", () => {
             ].forEach(prefix => {
                 const message = `${prefix}foo`;
 
-                test(`Posts failure status if the commit message has invalid tag prefix: "${prefix}"`, async () => {
+                test(`Posts failure status if the PR title has invalid tag prefix: "${prefix}"`, async () => {
                     mockSingleCommitWithMessage(message);
 
                     const nockScope = nock("https://api.github.com")
@@ -280,7 +338,7 @@ describe("commit-message", () => {
                         })
                         .reply(200);
 
-                    await emitBotEvent(bot, { action });
+                    await emitBotEvent(bot, { action, pull_request: { number: 1, title: message, user: { login: "user-a" } } });
                     expect(nockScope.isDone()).toBeTruthy();
                     expect(nockScope2.isDone()).toBeTruthy();
                 });
@@ -309,7 +367,7 @@ describe("commit-message", () => {
             TAG_LABELS.forEach((labels, prefix) => {
                 const message = `${prefix} foo`;
 
-                test(`Posts success status if the commit message has valid tag prefix: "${prefix}"`, async () => {
+                test(`Posts success status if the PR title has valid tag prefix: "${prefix}"`, async () => {
                     mockSingleCommitWithMessage(message);
 
                     const labelsScope = mockLabels(labels);
@@ -317,7 +375,7 @@ describe("commit-message", () => {
                         .post("/repos/test/repo-test/statuses/first-sha", req => req.state === "success")
                         .reply(201);
 
-                    await emitBotEvent(bot, { action });
+                    await emitBotEvent(bot, { action, pull_request: { number: 1, title: message, user: { login: "user-a" } } });
                     expect(nockScope.isDone()).toBeTruthy();
                     expect(labelsScope.isDone()).toBeTruthy();
                 });
diff --git a/tests/plugins/release-monitor/index.js b/tests/plugins/release-monitor/index.js
index 9178ab0..e1f26a7 100644
--- a/tests/plugins/release-monitor/index.js
+++ b/tests/plugins/release-monitor/index.js
@@ -726,7 +726,7 @@ describe("release-monitor", () => {
                         },
                         pull_request: {
                             number: 1,
-                            title: "New: add 1"
+                            title: "Fix: add 1"
                         },
                         repository: {
                             name: "repo-test",
diff --git a/tests/plugins/utils.js b/tests/plugins/utils.js
deleted file mode 100644
index 44996ad..0000000
--- a/tests/plugins/utils.js
+++ /dev/null
@@ -1,45 +0,0 @@
-"use strict";
-
-const utils = require("../../src/plugins/utils");
-
-const COMMIT_MESSAGE = "Commit message";
-const PULL_REQUEST_TITLE = "PR title";
-
-const SINGLE_COMMIT = [
-    {
-        commit: {
-            message: COMMIT_MESSAGE
-        }
-    }
-];
-
-const MULTIPLE_COMMITS = [
-    {
-        commit: {
-            message: COMMIT_MESSAGE
-        }
-    },
-    {
-        commit: {
-            message: COMMIT_MESSAGE
-        }
-    }
-];
-
-const PULL_REQUEST = {
-    title: PULL_REQUEST_TITLE
-};
-
-describe("utils", () => {
-    describe("getCommitMessageForPR", () => {
-        test("Should return first commit summary if PR has one commit", () => {
-            expect(utils.getCommitMessageForPR(SINGLE_COMMIT, PULL_REQUEST))
-                .toBe(COMMIT_MESSAGE);
-        });
-
-        test("Should return PR title if PR has multiple commits", () => {
-            expect(utils.getCommitMessageForPR(MULTIPLE_COMMITS, PULL_REQUEST))
-                .toBe(PULL_REQUEST_TITLE);
-        });
-    });
-});