Permalink
Browse files

add Github templates for issues and PRs (#216)

  • Loading branch information...
waehlisch committed Feb 11, 2019
1 parent ef8930d commit b99a0104dea71a4332ae2bad550b7ab98e44cf91
@@ -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! -->

@@ -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! -->

@@ -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! -->

@@ -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/.
-->

0 comments on commit b99a010

Please sign in to comment.