convert md issue templates into yml

Author: TheSnoozer

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,54 @@
+name: Bug Report
+description: Create a bug report to help us fix an issue
+labels: [ "bug", "to-triage" ]
+assignees: [ ]
+body:
+    - type: markdown
+      attributes:
+          value: |
+              Please follow the instructions below.
+              We will close issues that don't provide enough information.
+    - type: textarea
+      id: describe-the-bug
+      attributes:
+          label: Describe the bug (required)
+          description: Please provide a brief summary of the issue and provide a summarised description in the title above.
+      validations:
+          required: true
+    - type: textarea
+      id: steps-to-reproduce
+      attributes:
+          label: Steps to Reproduce (required)
+          description: |
+              Please provide all the steps to experience the issue.
+          value: |
+              I run the plugin with ``mvn clean deploy`` VS ``mvn deploy:deploy``...
+      validations:
+          required: true
+    - type: textarea
+      id: steps-to-reproduce-public-project
+      attributes:
+          label: Is there a (public) project where this issue can be reproduced? (optional)
+          description: |
+              You can use [this template](https://github.com/TheSnoozer/git-commit-id-debugging) to showcase your problem.
+      validations:
+          required: false
+    - type: textarea
+      id: environment
+      attributes:
+          label: Your Environment (optional)
+          description: |
+              Include as many relevant details about the environment you experienced the bug in.
+              Are you running inside Windows Terminal, Powershell, Git Bash, /bin/bash, ...?
+              On what Operating System you experience the bug (on Linux run ``lsb_release -a`` or ``cat /etc/*release*``)?
+      validations:
+          required: false
+    - type: textarea
+      id: context
+      attributes:
+          label: Context (optional)
+          description: |
+              Feel free to add any other context or screenshots about the bug.
+              How are you affected? What is your goal? Anything else?
+      validations:
+          required: false

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,36 @@
+name: Feature request
+description: Suggest an idea for this project
+labels: [ "enhancement", "to-triage" ]
+assignees: [ ]
+body:
+    - type: markdown
+      attributes:
+          value: |
+              Please follow the instructions below.
+              We will close issues that don't provide enough information.
+    - type: textarea
+      id: describe-the-idea
+      attributes:
+          label: Describe the idea (required)
+          description: Please provide a brief summary of your idea and provide a summarised description in the title above.
+      validations:
+          required: true
+    - type: textarea
+      id: expected-behaviour
+      attributes:
+          label: Tell us about the expected behaviour (required)
+          description: |
+              If you're suggesting a change/improvement, tell us a bit more about the problem you attempt to solve and how you idea helps to solve it.
+              Include a brief description of what you think should happen, maybe even how it should work and how you plan on using it.
+              Ex. I'm always frustrated when [...]
+      validations:
+          required: true
+    - type: textarea
+      id: context
+      attributes:
+          label: Context (optional)
+          description: |
+              Feel free to add any other context or screenshots about the feature.
+              How are you affected? What is your goal? Anything else?
+      validations:
+          required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,44 @@
+name: New release request
+description: Will be created by the author of the plugin, so not relevant for the public :-)
+labels: [ ]
+assignees: [ ]
+body:
+    - type: textarea
+      id: describe-the-release
+      attributes:
+          label: Describe the release details (required)
+          description: |
+              Just submit this as new issue...
+          value: |
+              This is the place holder to release the new 6.0.0 version.
+              Previous releases can be found under https://repo1.maven.org/maven2/io/github/git-commit-id/git-commit-id-plugin-core/
+
+              Note that the current open tickets should be addressed, before performing a release.
+
+              # General scope of the new release:
+              Fixed some minor things, added some minor features...(full list https://github.com/git-commit-id/git-commit-id-plugin-core//issues?q=milestone%3A6.0.0-rc.2).
+
+              # Release-Guide
+              see http://central.sonatype.org/pages/ossrh-guide.html
+
+              - [ ] verify that `~/.m2/settings.xml` exists and contains username/password which is required as per https://central.sonatype.org/publish/publish-maven/#distribution-management-and-authentication
+              - [ ] update dependencies `mvn versions:display-dependency-updates`
+              - [ ] wait for github actions to pass
+              - [ ] `mvn release:prepare`
+                    [INFO] Checking dependencies and plugins for snapshots ...
+                    What is the release version for "Git Commit Id Plugin Core"? (io.github.git-commit-id:git-commit-id-plugin-core) **6.0.0**: : [ENTER]
+                    What is SCM release tag or label for "Git Commit Id Plugin Core"? (io.github.git-commit-id:git-commit-id-plugin-core) git-commit-id-plugin-core-6.0.0: : **v6.0.0** [ENTER]
+                    What is the new development version for "Git Commit Id Plugin Core"? (io.github.git-commit-id:git-commit-id-plugin-core) **6.0.1-SNAPSHOT**: : [ENTER]
+              - [ ] wait for github actions to pass
+              - [ ] `mvn release:perform`
+                    - (or `mvn clean source:jar javadoc:jar deploy -Pgpg` from the git tag)
+                    - (or `mvn release:perform -Dresume=false`)
+                    - Note: If the uploading of the artifacts fails, ensure that a [`settings.xml`](https://github.com/git-commit-id/git-commit-id-maven-plugin/blob/master/.buildscript/settings.xml) exists under the local `.m2`-Folder
+              - [ ] then go to https://s01.oss.sonatype.org/ log in there and go to the staging repositories, there will be the plugin, you have to first close and then release it if validation passed.
+              - [ ] verify plugin is available on (might take some time) https://repo1.maven.org/maven2/io/github/git-commit-id/git-commit-id-plugin-core/
+              - [ ] under [Milestones](https://github.com/git-commit-id/git-commit-id-plugin-core/milestones) close old milestone
+              - [ ] under [Milestones](https://github.com/git-commit-id/git-commit-id-plugin-core/milestones) create new milestone for new version
+              - [ ] under [Releases](https://github.com/git-commit-id/git-commit-id-plugin-core/releases) publish Release-Notes
+              - [ ] update readme to point to the latest version available
+      validations:
+          required: true