4 files changed, 108 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..b3d4372
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,39 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+### Description
+<!--
+Example: Uninitialized use of stack variables in rtr_sync_receive_and_store_pdus.
+-->
+
+### Steps to reproduce the issue
+<!--
+Try to describe as precisely as possible the steps required to reproduce
+the issue. Here, you can also describe your RTRlib configuration (e.g., to
+which cache server you connect).
+-->
+
+### Expected results
+<!--
+Example: The variables `pfx_shadow_table` and `spki_shadow_table` in
+`packets.c:rtr_sync_receive_and_store_pdus` should be initialized at least
+with `NULL`.
+-->
+
+### Actual results
+<!--
+Please paste or specifically describe the actual output and implications.
+-->
+
+### Versions
+<!--
+Operating system: Mac OSX, Linux
+Build environment: GCC
+RPKEI Cache server (optional): Routinator, RIPE Validator, rpki.net etc.
+-->
+
+<!-- Thanks for contributing! -->
+
diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/enhancement.md
new file mode 100644
index 0000000..6b7c217
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/enhancement.md
@@ -0,0 +1,17 @@
+---
+name: Enhancement Request
+about: Ask for the enhancement of an existing feature.
+
+---
+
+### Description of current state
+<!-- Please describe the current state and why it is important to enhance. -->
+
+### Improvement
+<!-- Please describe the enhancement. -->
+
+### Useful links
+<!-- Please include links to any documentation that you think is useful. -->
+
+<!-- Thanks for contributing! -->
+
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 0000000..398efac
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,15 @@
+---
+name: Feature Request
+about: Ask for missing features.
+
+---
+
+### Description
+<!-- Please describe your use case, why you need this feature, and why this
+feature is important for RTRlib. -->
+
+### Useful links
+<!-- Please include links to any documentation that you think is useful. -->
+
+<!-- Thanks for contributing! -->
+
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..e5d42cc
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,37 @@
+<!--
+The RTRlib community cares about code quality. Therefore, before
+describing what your contribution is about, we would like you to make sure
+that your modifications are compliant with the RTRlib coding conventions, see
+https://github.com/rtrlib/rtrlib/blob/master/CONTRIBUTING.
+-->
+
+### Contribution description
+
+<!--
+Put here the description of your contribution:
+- describe which part(s) of RTRlib is (are) involved
+- if this is a bug fix, describe the bug that it solves and how it is solved
+- you can also give more information to reviewers about how to test your changes
+-->
+
+
+### Testing procedure
+
+<!--
+Details steps to test your contribution:
+- which test/example to compile and is there a 'test' command
+- how to know that it was not working/available in master
+- the expected success of the test output
+-->
+
+
+### Issues/PRs references
+
+<!--
+Examples: Fixes #212. See also #196. Depends on PR #188.
+
+Please use keywords (e.g., fixes, resolve) with the links to the issues you
+resolved. This way they will be automatically closed when your pull request
+is merged. See https://help.github.com/articles/closing-issues-using-keywords/.
+-->
+