chore(build): issues/543 jira for commits (#566)

* commit lint, allow jira issues * contributing, commit format
RedHatInsights · Feb 16, 2021 · a4b5cda · a4b5cda
1 parent 87080ad
commit a4b5cda
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 0 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -51,6 +51,16 @@ It's required that commit messaging follow the format
    <type>[optional scope]: <issue number><description>
 ```
 
+For Jira issues that looks like
+```
+   <type>[optional scope]: ent-123 <description>
+```
+
+For Github issues that looks like
+```
+   <type>[optional scope]: issues/123 <description>
+```
+
 Settings for [Standard Version](https://github.com/conventional-changelog/standard-version#readme) can be found in [package.json](./package.json)
 
 ### Branching, Pull Requests, and Releases

diff --git a/scripts/actions.commit.js b/scripts/actions.commit.js
@@ -54,6 +54,7 @@ const messagesList = parsedMessages =>
 
     const issueNumberValid =
       (/(^issues\/[\d,]+$)/.test(issueNumber) && 'valid') ||
+      (/(^ent-[\d,]+$)/.test(issueNumber) && 'valid') ||
       (issueNumberException && 'valid') ||
       'INVALID: issue number';