diff options
Diffstat (limited to 'src/jaegertracing/jaeger-client-cpp/.github')
| -rw-r--r-- | src/jaegertracing/jaeger-client-cpp/.github/ISSUE_TEMPLATE.md | 28 | ||||
| -rw-r--r-- | src/jaegertracing/jaeger-client-cpp/.github/PULL_REQUEST_TEMPLATE.md | 18 |
2 files changed, 46 insertions, 0 deletions
diff --git a/src/jaegertracing/jaeger-client-cpp/.github/ISSUE_TEMPLATE.md b/src/jaegertracing/jaeger-client-cpp/.github/ISSUE_TEMPLATE.md new file mode 100644 index 000000000..7a5851ba9 --- /dev/null +++ b/src/jaegertracing/jaeger-client-cpp/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,28 @@ +<!-- +Welcome to the Jaeger project! 👋🎉 + +- Please search for existing issues to avoid creating duplicate bugs/feature requests. +- Please be respectful and considerate of others when commenting on issues. +- Please provide as much information as possible so we all understand the issue. +- If you only have a question, you may get a faster response by asking in + - our chat room https://gitter.im/jaegertracing/Lobby, or + - the forum https://groups.google.com/d/forum/jaeger-tracing + (but please don't double post) +--> + +## Requirement - what kind of business use case are you trying to solve? + +<!-- required section --> + +## Problem - what in Jaeger blocks you from solving the requirement? + +<!-- required section --> +<!-- If possible, describe the impact of the problem. --> + +## Proposal - what do you suggest to solve the problem or improve the existing situation? + +<!-- It's ok if you don't have one. --> + +## Any open questions to address + +<!-- Questions that should be answered before proceeding with implementation. --> diff --git a/src/jaegertracing/jaeger-client-cpp/.github/PULL_REQUEST_TEMPLATE.md b/src/jaegertracing/jaeger-client-cpp/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 000000000..2564119cc --- /dev/null +++ b/src/jaegertracing/jaeger-client-cpp/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,18 @@ +<!-- +We appreciate your contribution to the Jaeger project! 👋🎉 + +Before creating a pull request, please make sure: +- Your PR is solving one problem +- You have read the guide for contributing + - See https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md +- You signed all your commits (otherwise we won't be able to merge the PR) + - See https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md#sign-your-work +- You added unit tests for the new functionality +- You mention in the PR description which issue it is addressing, e.g. "Resolves #123" +--> + +## Which problem is this PR solving? +- + +## Short description of the changes +- |