From ee4cfd66d66038bf1c73b2dbbb15f1f936f63114 Mon Sep 17 00:00:00 2001
From: Benjamin Goering <171782+gobengo@users.noreply.github.com>
Date: Tue, 13 Sep 2022 20:43:20 -0700
Subject: [PATCH] add ci workflow conventional-commits.yml

---
 .github/workflows/conventional-commits.yml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 .github/workflows/conventional-commits.yml

diff --git a/.github/workflows/conventional-commits.yml b/.github/workflows/conventional-commits.yml
new file mode 100644
index 0000000..2197b14
--- /dev/null
+++ b/.github/workflows/conventional-commits.yml
@@ -0,0 +1,22 @@
+name: 'Check Conventional Commits'
+
+on:
+  # `pull_request_target` event runs in the context of the base of the pull request, rather than in the context of the merge commit, as the pull_request event does. 
+  # This prevents execution of unsafe code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. 
+  # This event allows your workflow to do things like label or comment on pull requests from forks.
+  # Avoid using this event if you need to build or run code from the pull request.
+  # https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+
+jobs:
+  main:
+    name: Validate PR title
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@v4
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}