ci: Add in repo automation for releases/issues (#125)

Author: fjuma

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,33 @@
+name: 🐞 Bug Report
+description: File a bug report
+title: "[Bug]: "
+type: "Bug"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for stopping by to let us know something could be better!
+        Private Feedback? Please use this [Google form](https://goo.gle/a2a-feedback)
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us what you expected to happen and how to reproduce the issue.
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/google-a2a/A2A?tab=coc-ov-file#readme)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,41 @@
+name: 💡 Feature Request
+description: Suggest an idea for this repository
+title: "[Feat]: "
+type: "Feature"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for stopping by to let us know something could be better!
+        Private Feedback? Please use this [Google form](https://goo.gle/a2a-feedback)
+  - type: textarea
+    id: problem
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is.
+      placeholder: Ex. I'm always frustrated when [...]
+  - type: textarea
+    id: describe
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/google-a2a/A2A?tab=coc-ov-file#readme)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+# Description
+
+Thank you for opening a Pull Request!
+Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
+
+- [ ] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
+- [ ] Make your Pull Request title in the <https://www.conventionalcommits.org/> specification.
+    - Important Prefixes for [release-please](https://github.com/googleapis/release-please):
+        - `fix:` which represents bug fixes, and correlates to a [SemVer](https://semver.org/) patch.
+        - `feat:` represents a new feature, and correlates to a SemVer minor.
+        - `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking change (indicated by the `!`) and will result in a SemVer major.
+- [ ] Ensure the tests pass
+- [ ] Appropriate READMEs were updated (if necessary)
+
+Fixes #<issue_number_goes_here> 🦕

.github/conventional-commit-lint.yaml

@@ -0,0 +1,2 @@
+enabled: true
+always_check_pr_title: true

.github/release-please.yml

@@ -0,0 +1,4 @@
+releaseType: maven
+handleGHRelease: true
+bumpMinorPreMajor: false
+bumpPatchForMinorPreMajor: true

.github/release-trigger.yml

@@ -0,0 +1 @@
+enabled: true