diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 00000000..dabc3e7f
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,7 @@
+Enhancement:
+
+Reason:
+
+Result:
+
+Issue Tracker Tickets (Jira or BZ if any):
diff --git a/.github/workflows/commitlint.yml b/.github/workflows/commitlint.yml
index 720b9542..ae3e73e6 100644
--- a/.github/workflows/commitlint.yml
+++ b/.github/workflows/commitlint.yml
@@ -24,20 +24,6 @@ jobs:
       - name: Install conventional-commit linter
         run: npm install @commitlint/config-conventional @commitlint/cli
 
-      # Finding the commit range is not as trivial as it may seem.
-      #
-      # At this stage, git's HEAD does not refer to the latest commit in the
-      # PR, but rather to the merge commit inserted by the PR. So instead we
-      # have to get 'HEAD' from the PR event.
-      #
-      # One cannot use the number of commits
-      # (github.event.pull_request.commits) to find the start commit
-      # i.e. HEAD~N does not work, this breaks if there are merge commits.
-      - name: Run commitlint on commits
-        run: >-
-          npx commitlint --from '${{ github.event.pull_request.base.sha }}'
-          --to '${{ github.event.pull_request.head.sha }}' --verbose
-
       - name: Run commitlint on PR title
         run: >-
           echo '${{ github.event.pull_request.title }}' |