GH Templates

.github/CONTRIBUTING.md

@@ -5,12 +5,7 @@ contributions from anyone on the internet, and are grateful for even the
 smallest of fixes!
 
 If you'd like to contribute to go-core, please fork, fix, commit and send a
-pull request for the maintainers to review and merge into the main code base. If
-you wish to submit more complex changes though, please check up with the core
-devs first on [our core talk](https://coretalk.info) to
-ensure those changes are in line with the general philosophy of the project
-and/or get some early feedback which can make both your efforts much lighter as
-well as our review and merge procedures quick and simple.
+pull request for the maintainers to review and merge into the main code base.
 
 ## Coding guidelines
 

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,72 @@
+name: Report Bug
+description: Create a bug report.
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please, provide as much details as possible to make proper evaluation and in the end resolve the bug report faster.
+
+  - type: markdown
+    attributes:
+      value: |
+        Software specific details.
+
+  - type: input
+    id: os
+    attributes:
+      label: OS and version
+      description: Name and version of OS used.
+      placeholder: OS
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Software version
+      description: Version of software used.
+      placeholder: Version
+    validations:
+      required: true
+
+  - type: textarea
+    id: bug
+    attributes:
+      label: Bug
+      description: Describe the Bug.
+      placeholder: Bug description
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Reproduce Bug
+      description: Steps to reproduce the behavior.
+      placeholder: 1. Step 1
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: Describe the result you are expecting.
+      placeholder: Result
+    validations:
+      required: true
+
+  - type: input
+    id: hash
+    attributes:
+      label: Commit hash
+      description: Commit hash if known.
+      placeholder: baf2aab0128f07262b564214ec70fc07befc6bb3
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+      description: Please, place additional content or screenshots.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Vulnerability report
+    url: https://dev.coreblockchain.cc/report/bug
+    about: To report vulnerabilty, please use this link.
+  - name: CIP
+    url: https://cip.coreblockchain.cc/
+    about: Core Improvement Proposals.
+  - name: Community Discussion
+    url: https://coretalk.space
+    about: Discussion about Blockchain.
+  - name: Blog
+    url: https://blog.coreblockchain.cc/
+    about: Basic information about Core Blockchain.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,43 @@
+name: Feature request
+description: Suggest an idea for this project.
+labels:
+  - feature
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Suggest an idea for this project and developers will consider the integration.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: Is your feature request related to a problem? Please describe.
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Solution
+      description: Describe the solution you'd like.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives
+      description: Describe alternatives you've considered.
+
+  - type: textarea
+    id: implementation
+    attributes:
+      label: Implementation
+      description: Describe implementation with example of the code.
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+      description: Please, place additional content or screenshots.

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,33 @@
+## Description
+<!-- Please include a summary of the change and which issue is fixed. -->
+<!-- Please also include relevant motivation and context. -->
+<!-- List any dependencies that are required for this change. -->
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change which fixes an issue).
+- [ ] New feature (non-breaking change which adds functionality).
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
+- [ ] This change requires a documentation update.
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+
+## Related Issue
+<!--- Please link to the issue here: -->
+
+## Checklist
+
+- [ ] My code follows the style guidelines of this project.
+- [ ] I have performed a self-review of my own code.
+- [ ] I have commented my code, particularly in hard-to-understand areas.
+- [ ] I have made corresponding changes to the documentation.
+- [ ] My changes generate no new warnings.
+- [ ] I have added tests that prove my fix is effective or that my feature works.
+- [ ] New and existing unit tests pass locally with my changes.
+- [ ] Any dependent changes have been merged and published in downstream modules.
+- [ ] I have checked my code and corrected any misspellings.