Skip to content

Commit 0213c4e

Browse files
GitHub issue and pull request templates (#53)
* GitHub issue templates This commit makes use of GitHub's feature to define multiple issue templates (1). The initial template file that has been used when the feature was introduced (2) and is now used as a fallback/generic template to redirect to one of the other specific templates. The UI helps users to open a new issue in projects by prompting them to choose from multiple issue types. References: (1) blog.github.com/2018-01-25-multiple-issue-and-pull-request-templates (2) blog.github.com/2016-02-17-issue-and-pull-request-templates Epic: GH-33 Depends on GH-49 GH-42 <---------------------------------------------------------------------> * GitHub pull request template This commit makes use of GitHub's feature to define multiple pull request templates (1). See the GitHub Help (2) for more details about issue and pull request templates. References: (1) blog.github.com/2016-02-17-issue-and-pull-request-templates (2) help.github.com/articles/about-issue-and-pull-request-templates Epic: GH-33 Depends on GH-49 Resolves GH-42
1 parent 30df86d commit 0213c4e

File tree

4 files changed

+183
-0
lines changed

4 files changed

+183
-0
lines changed

.github/ISSUE_TEMPLATE.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
2+
3+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/snowsaw/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
4+
5+
## [Please follow one of the issue templates](https://github.com/arcticicestudio/snowsaw/issues/new/choose)
6+
7+
To keep the backlog clean and actionable, issues should be opened using [one the provided issue templates](https://github.com/arcticicestudio/snowsaw/issues/new/choose) to help maintainers and the community to understand it, find related reports and to resolve tickets faster.
8+
9+
### Support
10+
11+
If you got a question or need help with any aspect of the project feel free to [join the community](https://spectrum.chat/arcticicestudio/snowsaw), write us on [Twitter](https://twitter.com/arcticicestudio) and ensure to read the [project documentations](https://github.com/arcticicestudio/snowsaw).
12+
13+
You can also search for already opened and related issue using the search for the [“question“](https://github.com/arcticicestudio/snowsaw/labels/type-question) issue label.

.github/ISSUE_TEMPLATE/bugs.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
name: Bug Report
3+
about: Report a bug that is caused by the code in this repository
4+
---
5+
6+
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
7+
8+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/snowsaw/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
9+
10+
## Prerequisites
11+
12+
This section and the instructions in the sections below are only part of this issue template. Please ensure to **delete this whole section, all pre-filled instructions of the sections below and sections you have not filled out before submitting** to ensure a clear structure and overview.
13+
14+
Please do your best to provide as much information as possible and use a clear and descriptive title for your bug report to help maintainers and the community understand and reproduce the behavior, find related reports and to resolve the ticket faster.
15+
16+
- **Ensure the bug has not already been reported by using the [GitHub Issues search](https://github.com/arcticicestudio/snowsaw/issues)** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one. If you find a closed issue that seems to be similar to this one, include a link to the original issue in the [metadata head](#metadata-head) section of this issue.
17+
- **Ensure the bug is reproducible and has not already been fixed** — use the [latest version](https://github.com/arcticicestudio/snowsaw/releases/latest) and [`develop`](https://github.com/arcticicestudio/snowsaw/tree/develop) branch.
18+
19+
## Metadata Head
20+
21+
The metadata head can be added to the top of the issue as [Markdown text quote](https://help.github.com/articles/basic-writing-and-formatting-syntax) containing the the ID of other related issues.
22+
23+
> Related issues:
24+
25+
## Description
26+
27+
Describe the bug as in many relevant details as possible with a clear and concise description. Ensure to fill in the [steps to reproduce](#steps-to-reproduce) it.
28+
29+
### Steps to Reproduce
30+
31+
1. Step One
32+
2. Step Two
33+
3. ...
34+
35+
### Expected Behavior
36+
37+
What you expect to happen?
38+
39+
### Actual Behavior
40+
41+
What actually happens?
42+
43+
## Example
44+
45+
Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/snowsaw/blob/develop/CONTRIBUTING.md#mcve)
46+
47+
**This is a optional section, but it can drastically increase the speed at which this issue can be processed since it takes away the time-consuming reconstruction to reproduce the bug.**
48+
The recommended way is to upload it as [Gist](https://gist.github.com) or new repository to GitHub, but of course you can [attach it to this issue](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests), use any free file hosting service or paste the code in [Markdown code blocks](https://help.github.com/articles/basic-writing-and-formatting-syntax) into this issue.
49+
50+
## Environment and Versions
51+
52+
- What is the version of snowsaw you are running?
53+
- What is the name and the version of your OS?
54+
- Have you tried to reproduce it on different OS environments and if yes, is the behavior the same for all?
55+
- Please provide the version of your [Go](https://golang.org) runtime.
56+
- Are you using any additional CLI arguments to run the project?
57+
- If you've installed the [mage](https://github.com/magefile/mage) build tool locally on your system, please specify the version.
58+
- Are you using any additional CLI arguments to start `mage` tasks other than defined by the project documentation?
59+
60+
Please run the following command **from within the project root** and paste the output in the code block below: `go env`
61+
62+
```md
63+
Paste output of the command here.
64+
```
65+
66+
## Stack Trace and Error Messages
67+
68+
```raw
69+
Paste the full stack trace, error messages or the logfile here.
70+
```
71+
72+
... or [attach them as files](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests) to this issue.
73+
74+
## Additional Context
75+
76+
Add any other context, screenshots or screencasts which are relevant for this issue.
77+
78+
## References
79+
80+
Add any other references and links which are relevant for this issue.
81+
82+
## Potential Solution
83+
84+
Maybe include the lines of code that you have identified as causing the bug or references to other projects where this bug has already been reported.
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
name: Enhancement Suggestions
3+
about: Submit an enhancement suggestion for new features or minor improvements to existing functionality
4+
---
5+
6+
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
7+
8+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/snowsaw/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
9+
10+
## Prerequisites
11+
12+
This section and the instructions in the sections below are only part of this issue template. Please ensure to **delete this whole section, all pre-filled instructions of the sections below and sections you have not filled out before submitting** to ensure a clear structure and overview.
13+
14+
Please do your best to provide as much information as possible and use a clear and descriptive title for your enhancement suggestion to help maintainers and the community understand and reproduce the behavior, find related reports and to resolve the ticket faster.
15+
16+
- **Ensure the enhancement has not already been reported by using the [GitHub Issues search](https://github.com/arcticicestudio/snowsaw/issues)** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one. If you find a closed issue that seems to be similar to this one, include a link to the original issue in the [metadata head](#metadata-head) section of this issue.
17+
- **Check if the enhancement has already been implemented** — use the [latest version](https://github.com/arcticicestudio/snowsaw/releases/latest) and [`develop`](https://github.com/arcticicestudio/snowsaw/tree/develop) branch to ensure that the feature or improvement has not already been added.
18+
19+
## Metadata Head
20+
21+
The metadata head can be added to the top of the issue as [Markdown text quote](https://help.github.com/articles/basic-writing-and-formatting-syntax) containing the ID of other related issues.
22+
23+
> Related issues:
24+
25+
## Description
26+
27+
Describe the enhancement in many relevant details as possible.
28+
29+
### Benefits
30+
31+
Add specific use-cases and explain why this feature or improvement would be useful and maybe include references to related known problems or bug reports.
32+
33+
### Possible Drawbacks
34+
35+
Describe possible negative impacts regarding e.g. functionality or usability.
36+
37+
### Alternative Solutions
38+
39+
If you've considered alternative features or solutions please describe it clearly and concise.
40+
41+
## Example
42+
43+
Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/snowsaw/blob/develop/CONTRIBUTING.md#mcve)
44+
45+
**This is a optional section, but it can drastically increase the speed at which this issue can be processed since it takes away the time-consuming reconstruction to reproduce the enhancement.**
46+
The recommended way is to upload it as [Gist](https://gist.github.com) or new repository to GitHub, but of course you can [attach it to this issue](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests), use any free file hosting service or paste the code in [Markdown code blocks](https://help.github.com/articles/basic-writing-and-formatting-syntax) into this issue.
47+
48+
## Additional Context
49+
50+
Add any other context, screenshots or screencasts which are relevant for this issue.
51+
52+
## References
53+
54+
Add any other references and links which are relevant for this issue.
55+
56+
## Potential Solution
57+
58+
Maybe include references to other projects where this enhancement already exists.

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
2+
3+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/snowsaw/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
4+
5+
## Prerequisites
6+
7+
This section and the instructions in the sections below are only part of this pull request template. Please ensure to **delete this whole section, all pre-filled instructions of the sections below and sections you have not filled out before submitting** to ensure a clear structure and overview.
8+
9+
Please do your best to provide as much information as possible and use a clear and descriptive title for your enhancement suggestion or bug fix to help maintainers and the community understand and reproduce the behavior, find related pull requests and to merge it faster.
10+
11+
- **Ensure the pull request has not already been submitted by using the [GitHub Issue search](https://github.com/arcticicestudio/snowsaw/issues)** — check if this enhancement or bug fix has already been suggested. If it has **and the pull request is still open**, add your additions as comment or [suggest a change](https://help.github.com/articles/incorporating-feedback-in-your-pull-request/#applying-a-suggested-change) to the existing pull request instead of opening a new one. If you find a closed pull request that seems to be similar to this one, include a link to the original pull request in the [metadata head](#metadata-head) section of this new pull request.
12+
- **Ensure to adhere to the [pull request contribution guidelines](https://github.com/arcticicestudio/snowsaw/blob/develop/CONTRIBUTING.md#pull-requests)**, especially the one for tests and documentations.
13+
- **Check if the enhancement has already been implemented or bug already fixed** — use the [latest version](https://github.com/arcticicestudio/snowsaw/releases/latest) and [`develop`](https://github.com/arcticicestudio/snowsaw/tree/develop) branch to ensure that the enhancement or bug fix has not already been added.
14+
15+
## Metadata Head
16+
17+
The metadata head should be added to the top of the pull request as [Markdown text quote](https://help.github.com/articles/basic-writing-and-formatting-syntax) containing the [GitHub issue keyword(s)](https://help.github.com/articles/closing-issues-using-keywords) to link to the related enhancements suggestions (`Closes`) or bug reports (`Fixes`). You can add additional details like dependencies to other pull requests and the order it needs to be merged.
18+
19+
> Closes ISSUE_ID
20+
> Must be merged **after**/**before** ISSUE_ID
21+
22+
## Description
23+
24+
Describe the changes as in many relevant details as possible. If this is a enhancement suggestion add specific use-cases and explain why this feature or improvement would be useful. If this is a bug fix ensure to provide a _before/after_ comparison by describing the current behavior and the new behavior.
25+
26+
## References
27+
28+
Add any other references and links which are relevant for this pull request.

0 commit comments

Comments
 (0)