Skip to content

Commit 554638e

Browse files
Merge pull request #1364 from sudiptog81/dev-sudiptog81
Add Issue and PR Templates
2 parents 57b2758 + f95299d commit 554638e

File tree

4 files changed

+141
-0
lines changed

4 files changed

+141
-0
lines changed
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
name: "\U0001F41B Bug Report"
3+
about: Create a bug report to help us improve
4+
---
5+
6+
<!--
7+
Thank you for reporting an issue with the Node.js image.
8+
9+
Please fill in as much of the template below as you're able.
10+
-->
11+
12+
## Environment
13+
14+
* **Platform**:
15+
* **Docker Version**:
16+
* **Node.js Version**:
17+
* **Image Tag**:
18+
19+
## Expected Behavior
20+
21+
<!--
22+
Tell us what should happen. If possible please provide textual output instead of screenshots.
23+
-->
24+
25+
## Current Behavior
26+
27+
<!--
28+
Tell us what happens instead of the expected behavior. If possible please provide textual output instead of screenshots.
29+
-->
30+
31+
## Possible Solution
32+
33+
<!--
34+
Suggest a fix/reason for the bug in case you have an idea.
35+
-->
36+
37+
## Steps to Reproduce
38+
39+
<!--
40+
Tell us about the steps you took to encounter this bug with the image.
41+
-->
42+
43+
## Additional Information
44+
45+
<!--
46+
Tell us anything else you think we should know.
47+
-->
48+
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
name: "\U0001F680 Feature Request"
3+
about: Suggest an idea for this project
4+
---
5+
6+
<!--
7+
Thank you for suggesting an idea to make the Node.js image better.
8+
9+
Please fill in as much of the template below as you're able.
10+
-->
11+
12+
## Problem
13+
14+
<!--
15+
Please describe the problem you are trying to solve.
16+
-->
17+
18+
## Solution
19+
20+
<!--
21+
Please describe the desired behavior.
22+
-->
23+
24+
## Alternatives to Consider
25+
26+
<!--
27+
Please describe alternative solutions or features you have considered.
28+
-->
29+

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Need help with Node.js?
4+
url: https://github.com/nodejs/help
5+
about: Please file an issue in our help repo.
6+
- name: Found a problem with Node.js beyond the API reference documentation?
7+
url: https://github.com/nodejs/nodejs.org/issues/new/choose
8+
about: Please file an issue in the Node.js website repository.
9+
- name: Want to report security issues or vulnerabilites?
10+
url: https://github.com/nodejs/docker-node/security/policy
11+
about: Please go through our policy for reporting CVEs and security issues.
12+
- name: Need help with common questions related to using Node.js with Docker?
13+
url: https://stackoverflow.com/questions/tagged/node.js%2bdocker%2bdockerfile
14+
about: Please visit Stack Overflow to explore related questions and answers.

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
<!--
2+
Provide a general summary of your changes in the Title above.
3+
-->
4+
5+
## Description
6+
7+
<!--
8+
Describe your changes in detail.
9+
-->
10+
11+
## Motivation and Context
12+
13+
<!--
14+
Why is this change required? What problem does it solve?
15+
If it fixes an open issue, please link to the issue here.
16+
-->
17+
18+
## Testing Details
19+
20+
<!--
21+
Please describe in detail how you tested your changes. Include details of
22+
your testing environment, and the tests you ran to see how your change
23+
affects other areas of the code, etc.
24+
-->
25+
26+
## Example Output(if appropriate)
27+
28+
## Types of changes
29+
30+
<!--
31+
What types of changes does your code introduce? Put an `x` in all the boxes that apply.
32+
-->
33+
34+
- [ ] Bug fix (non-breaking change which fixes an issue)
35+
- [ ] New feature (non-breaking change which adds functionality)
36+
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
37+
38+
## Checklist
39+
40+
<!--
41+
Go over all the following points, and put an `x` in all the boxes that apply.
42+
If you're unsure about any of these, don't hesitate to ask. We're here to help!
43+
-->
44+
45+
- [ ] My code follows the code style of this project.
46+
- [ ] My change requires a change to the documentation.
47+
- [ ] I have updated the documentation accordingly.
48+
- [ ] I have read the **CONTRIBUTING.md** document.
49+
- [ ] All new and existing tests passed.
50+

0 commit comments

Comments
 (0)