Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.

Commit

Permalink
Adding new issue and PR template (#114)
Browse files Browse the repository at this point in the history
* Adding new issue and pull request template

Signed-off-by: Prakriti <prakritibansal98@gmail.com>

* Modifying URL in PULL_REQUEST_TEMPLATE

Signed-off-by: Prakriti <prakritibansal98@gmail.com>
  • Loading branch information
PikBot authored and yurishkuro committed Jun 14, 2018
1 parent f88e8fe commit fdc3b86
Show file tree
Hide file tree
Showing 2 changed files with 46 additions and 0 deletions.
28 changes: 28 additions & 0 deletions .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. -->
18 changes: 18 additions & 0 deletions .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
-

0 comments on commit fdc3b86

Please sign in to comment.