From 0004c15fa777e0fcf1754675388463c58965827f Mon Sep 17 00:00:00 2001
From: Krishna Kumar S <71367204+Krishks369@users.noreply.github.com>
Date: Tue, 19 Jul 2022 20:15:53 +0530
Subject: [PATCH] Update lint_PR.yml

---
 .github/workflows/lint_PR.yml | 21 +++++++--------------
 1 file changed, 7 insertions(+), 14 deletions(-)

diff --git a/.github/workflows/lint_PR.yml b/.github/workflows/lint_PR.yml
index dd8bd5c..1dbb90e 100644
--- a/.github/workflows/lint_PR.yml
+++ b/.github/workflows/lint_PR.yml
@@ -1,23 +1,16 @@
 
 on: [pull_request_target]
-
-jobs: 
-   publish:
-     runs-on: ubuntu-latest
-     
-     steps:
-     - name: Lint Specifier
-       uses: thollander/actions-comment-pull-request@v1
-       with: 
-         message: |
+uses: thollander/actions-comment-pull-request@v1
+with: 
+   message: |
          
-                ##Conventional commits
+       ##Conventional commits
 
-                Our repositories follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification. Releasing to GitHub and NPM is done with the support of [semantic-release](https://semantic-release.gitbook.io/semantic-release/).
+       Our repositories follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification. Releasing to GitHub and NPM is done with the support of [semantic-release](https://semantic-release.gitbook.io/semantic-release/).
 
-                Pull requests should have a title that follows the specification, otherwise, merging is blocked. If you are not familiar with the specification simply ask maintainers to modify. You can also use this cheatsheet if you want:
+       Pull requests should have a title that follows the specification, otherwise, merging is blocked. If you are not familiar with the specification simply ask maintainers to modify. You can also use this cheatsheet if you want:
 
-                - `fix: ` prefix in the title indicates that PR is a bug fix and PATCH release must be triggered.
+       - `fix: ` prefix in the title indicates that PR is a bug fix and PATCH release must be triggered.
                 - `feat: ` prefix in the title indicates that PR is a feature and MINOR release must be triggered.
                 - `docs: ` prefix in the title indicates that PR is only related to the documentation and there is no need to trigger release.
                 - `chore: ` prefix in the title indicates that PR is only related to cleanup in the project and there is no need to trigger release.