This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add issue and PR templates to the repo
- Loading branch information
Michael O'Keefe
committed
Sep 5, 2019
1 parent
2c45fad
commit 223af21
Showing
3 changed files
with
81 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
name: "Bug report" | ||
about: "Report a bug in Inferno" | ||
--- | ||
|
||
Thank you for reporting a possible bug in Inferno! Please fill in as much of the template below as you can. | ||
|
||
**Subject of the issue** | ||
Describe your issue here. | ||
|
||
|
||
|
||
**Your environment** | ||
* Edition of inferno (Community or Program): | ||
* Version of inferno: | ||
* Which browser and version(s) is the bug present on?: | ||
|
||
|
||
**Steps to reproduce** | ||
Tell us how to reproduce this issue. | ||
|
||
Include: | ||
|
||
* The selected test suite | ||
* The URL of the FHIR server being tested | ||
* The Test ID, if it's a problem with a specific test. | ||
* Any required configuration options (client ID, client secret, etc.) | ||
* Anything else needed to make the issue occur | ||
|
||
|
||
**Expected behaviour** | ||
Tell us what should happen | ||
|
||
|
||
|
||
**Actual behaviour** | ||
Tell us what happens instead. Include screenshots if possible. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
name: "Feature Request" | ||
about: "Request a feature you would like to be added to Inferno" | ||
--- | ||
|
||
**Is your feature request related to a problem? Please describe it.** | ||
Describe the problem you are trying to solve. | ||
|
||
**Describe the solution you'd like to see implemented** | ||
Things you can put in this section include (but aren't limited to): | ||
* A description of the solution. | ||
* Details of the technical implementation, if you've thought about it. | ||
* Any caveats/tradeoffs of the proposed solution. | ||
|
||
**Describe alternatives you've considered** | ||
Describe any alternative solutions or features you have considered. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
Pull requests into Inferno require the following items to be completed. Submitter and reviewer | ||
should check the relevant check boxes when the associated item is done. For items that are not | ||
applicable, note it's not applicable ("N/A") and check the box. For example, external Pull | ||
Requests do not require ticket links. | ||
|
||
**Submitter:** | ||
- [ ] This pull request describes why these changes were made. | ||
- [ ] Internal ticket for this PR: | ||
- [ ] Internal ticket links to this PR | ||
- [ ] Internal ticket is properly labeled (Community/Program) | ||
- [ ] Code diff has been reviewed for extraneous/missing code | ||
- [ ] Tests are included and test edge cases | ||
- [ ] Tests/code quality metrics have been run locally and pass | ||
|
||
|
||
**Reviewer 1:** | ||
|
||
Name: | ||
- [ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task's purpose | ||
- [ ] The tests appropriately test the new code, including edge cases | ||
- [ ] You have tried to break the code | ||
|
||
**Reviewer 2:** | ||
|
||
Name: | ||
- [ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task's purpose | ||
- [ ] The tests appropriately test the new code, including edge cases | ||
- [ ] You have tried to break the code |