fix(cicd): change new-feature template to yml

.github/ISSUE_TEMPLATE/bug.yml

@@ -1,7 +1,11 @@
 name: Bug
 description: File a bug report
 title: "[BUG] <title>"
+<<<<<<< HEAD
 labels: ["bug", "documentation", "core", "enhancement"]
+=======
+labels: ["bug", "documentation", "cicd", "core", "enhancement"]
+>>>>>>> 90f6a91 ( change new-feature template to yml)
 projects: ["Shoes Project"]
 assignees:
   - kirubeltadesse

.github/ISSUE_TEMPLATE/new_story.yml

@@ -1,7 +1,7 @@
 name: New Feature
 description: A new feature that needs to be developed
 title: "[UI/CORE] <title>"
-labels: ["bug", "cicd", "ui", "core"]
+labels: ["new-feature", "documentation", "cicd", "core", "enhancement"]
 projects: ["Shoes Project"]
 assignees:
   - kirubeltadesse

.github/pull_request_template.md

@@ -1,6 +1,10 @@
 ---
 name: "feat(core): <description>"
+<<<<<<< HEAD
 about: "Use this template for setting up your PR description"
+=======
+about: "Use this template for setting up your PR description."
+>>>>>>> 90f6a91 ( change new-feature template to yml)
 title: "Add support for the new feature"
 labels: bug, enhancement, customer-request
 assignees: self

.github/workflows/semantic-pr.yml

@@ -19,49 +19,66 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
-                # Configure which types are allowed (newline-delimited).
-                # Default: https://github.com/commitizen/conventional-commit-types
-                types: |
-                  fix
-                  feat
-                # Configure which scopes are allowed (newline-delimited).
-                # These are regex patterns auto-wrapped in `^ $`.
-                scopes: |
-                  core
-                  ui
-                  cicd
-                  fix #\d+
-                # Configure that a scope must always be provided.
-                requireScope: true
-                # Configure which scopes are disallowed in PR titles (newline-delimited).
-                # For instance by setting the value below, `chore(release): ...` (lowercase)
-                # and `ci(e2e,release): ...` (unknown scope) will be rejected.
-                # These are regex patterns auto-wrapped in `^ $`.
-                disallowScopes: |
-                  release
-                  [A-Z]+
-                # Configure additional validation for the subject based on a regex.
-                # This example ensures the subject doesn't start with an uppercase character.
-                subjectPattern: ^(?![A-Z]).+$
-                # If `subjectPattern` is configured, you can use this property to override
-                # the default error message that is shown when the pattern doesn't match.
-                # The variables `subject` and `title` can be used within the message.
-                subjectPatternError: |
-                  The subject "{subject}" found in the pull request title "{title}"
-                  didn't match the configured pattern. Please ensure that the subject
-                  doesn't start with an uppercase character.
-
-                # If the PR contains one of these newline-delimited labels, the
-                # validation is skipped. If you want to rerun the validation when
-                # labels change, you might want to use the `labeled` and `unlabeled`
-                # event triggers in your workflow.
-                ignoreLabels: |
-                  bot
-                  ignore-semantic-pull-request
-                # If you're using a format for the PR title that differs from the traditional Conventional
-                # Commits spec, you can use these options to customize the parsing of the type, scope and
-                # subject. The `headerPattern` should contain a regex where the capturing groups in parentheses
-                # correspond to the parts listed in `headerPatternCorrespondence`.
-                # See: https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-commits-parser#headerpattern
-                headerPattern: '^(\w*)(?:\(([\w$.\-*/ ]*)\))?: (.*)$'
-                headerPatternCorrespondence: type, scope, subject
+          # Configure which types are allowed (newline-delimited).
+          # Default: https://github.com/commitizen/conventional-commit-types
+          types: |
+            fix
+            feat
+            nf
+            docs
+            style
+            refactor
+            perf
+            test
+            build
+            ci
+            chore
+            revert
+          # Configure which scopes are allowed (newline-delimited).
+          # These are regex patterns auto-wrapped in `^ $`.
+          scopes: |
+            core
+            ui
+            cicd
+            fix #\d+
+          # Allow use of Merge commits (eg on github: "Merge branch 'master' into feature/ride-unicorns")
+          # this is only relevant when using commitsOnly: true (or titleAndCommits: true)
+          allowMergeCommits: true
+
+          # Allow use of Revert commits (eg on github: "Revert "feat: ride unicorns"")
+          # this is only relevant when using commitsOnly: true (or titleAndCommits: true)
+          allowRevertCommits: true
+
+          # Configure that a scope must always be provided.
+          requireScope: true
+          # Configure which scopes are disallowed in PR titles (newline-delimited).
+          # For instance by setting the value below, `chore(release): ...` (lowercase)
+          # and `ci(e2e,release): ...` (unknown scope) will be rejected.
+          # These are regex patterns auto-wrapped in `^ $`.
+          disallowScopes: |
+            release
+            [A-Z]+
+          # Configure additional validation for the subject based on a regex.
+          # This example ensures the subject doesn't start with an uppercase character.
+          subjectPattern: ^(?![A-Z]).+$
+          # If `subjectPattern` is configured, you can use this property to override
+          # the default error message that is shown when the pattern doesn't match.
+          # The variables `subject` and `title` can be used within the message.
+          subjectPatternError: |
+            The subject "{subject}" found in the pull request title "{title}"
+            didn't match the configured pattern. Please ensure that the subject
+            doesn't start with an uppercase character.
+          # If the PR contains one of these newline-delimited labels, the
+          # validation is skipped. If you want to rerun the validation when
+          # labels change, you might want to use the `labeled` and `unlabeled`
+          # event triggers in your workflow.
+          ignoreLabels: |
+            bot
+            ignore-semantic-pull-request
+          # If you're using a format for the PR title that differs from the traditional Conventional
+          # Commits spec, you can use these options to customize the parsing of the type, scope and
+          # subject. The `headerPattern` should contain a regex where the capturing groups in parentheses
+          # correspond to the parts listed in `headerPatternCorrespondence`.
+          # See: https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-commits-parser#headerpattern
+          headerPattern: '^(\w*)(?:\(([\w$.\-*/ ]*)\))?: (.*)$'
+          headerPatternCorrespondence: type, scope, subject