Skip to content

Commit e4fab23

Browse files
mtrezzamtrezza
authored
updated issue and PR templates (#1741)
* updated issue and PR templates * added browser info * updated wording
1 parent 92fe6a5 commit e4fab23

File tree

5 files changed

+132
-16
lines changed

5 files changed

+132
-16
lines changed

‎.github/ISSUE_TEMPLATE.md

-16
This file was deleted.

‎.github/ISSUE_TEMPLATE/---1-report-an-issue.md

+63
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
name: "\U0001F41B Report an issue"
3+
about: A feature is not working as expected.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### New Issue Checklist
11+
<!--
12+
Check every following box [x] before submitting your issue.
13+
Click the "Preview" tab for better readability.
14+
Thanks for contributing to Parse Platform!
15+
-->
16+
17+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
18+
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md).
19+
- [ ] I have searched through [existing issues](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
20+
- [ ] I can reproduce the issue with the [latest version of Parse Server](https://github.com/parse-community/parse-server/releases).
21+
- [ ] I can reproduce the issue with the [latest version of Parse Dashboard](https://github.com/parse-community/parse-dashboard/releases).
22+
23+
### Issue Description
24+
<!-- What is the specific issue? -->
25+
26+
### Steps to reproduce
27+
<!-- How can someone else reproduce the issue? -->
28+
29+
### Actual Outcome
30+
<!-- What outcome did you get? -->
31+
32+
### Expected Outcome
33+
<!-- What outcome did you expect? -->
34+
35+
### Failing Test / Pull Request
36+
<!--
37+
Please submit a PR with a failing test (or passing test if you already include the fix), so we can verify that the issue exists.
38+
-->
39+
40+
- PR with [test](https://github.com/parse-community/parse-server/blob/master/CONTRIBUTING.md#environment-setup): #`FILL_THIS_OUT`
41+
42+
### Environment
43+
<!-- Be specific with versions, don't use "latest" or semver ranges like "~x.y.z" or "^x.y.z". -->
44+
45+
Dashboard
46+
- Parse Dashboard version: `FILL_THIS_OUT`
47+
- Browser (Safari, Chrome, Firefox, Edge, etc.): `FILL_THIS_OUT`
48+
- Browser version: `FILL_THIS_OUT`
49+
50+
Server
51+
- Parse Server version: `FILL_THIS_OUT`
52+
- Operating system: `FILL_THIS_OUT`
53+
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): `FILL_THIS_OUT`
54+
55+
Database
56+
- System (MongoDB or Postgres): `FILL_THIS_OUT`
57+
- Database version: `FILL_THIS_OUT`
58+
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): `FILL_THIS_OUT`
59+
60+
### Logs
61+
<!--
62+
Include relevant logs here. Turn on additional logging by configuring VERBOSE=1 in your environment. If you get a Browser JavaScript error run `npm run dev` to see source maps and a more detailed stack trace.
63+
-->

‎.github/ISSUE_TEMPLATE/---2-feature-request.md

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: "\U0001F4A1 Request a feature"
3+
about: Suggest new functionality or an enhancement of existing functionality.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### New Feature / Enhancement Checklist
11+
<!--
12+
Check every following box [x] before submitting your issue.
13+
Click the "Preview" tab for better readability.
14+
Thanks for contributing to Parse Platform!
15+
-->
16+
17+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
18+
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md).
19+
- [ ] I have searched through [existing issues](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
20+
21+
### Current Limitation
22+
<!-- Which current limitation is the feature or enhancement addressing? -->
23+
24+
### Feature / Enhancement Description
25+
<!-- What is the concept of the functionality and how should it be implemented? -->
26+
27+
### Example Use Case
28+
<!-- What is an example use case in steps (1. / 2. / 3. / etc.) that describes the functionality? -->
29+
30+
### Alternatives / Workarounds
31+
<!-- Which alternatives or workarounds exist currently? -->
32+
33+
### 3rd Party References
34+
<!-- Have you seen a similar functionality provided somewhere else? -->

‎.github/ISSUE_TEMPLATE/config.yml

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: 🙋🏽‍♀️ Getting help with code
4+
url: https://stackoverflow.com/questions/tagged/parse-platform
5+
about: Get help with code-level questions on Stack Overflow.
6+
- name: 🙋 Getting general help
7+
url: https://community.parseplatform.org
8+
about: Get help with other questions on our Community Forum.

‎.github/pull_request_template.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
### New Pull Request Checklist
2+
<!--
3+
Please check the following boxes [x] before submitting your issue.
4+
Click the "Preview" tab for better readability.
5+
Thanks for contributing to Parse Server!
6+
-->
7+
8+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
9+
- [ ] I am creating this PR in reference to an [issue](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
10+
11+
### Issue Description
12+
<!-- Add a brief description of the issue this PR solves. -->
13+
14+
Related issue: #`FILL_THIS_OUT`
15+
16+
### Approach
17+
<!-- Add a description of the approach in this PR. -->
18+
19+
### TODOs before merging
20+
<!--
21+
Add TODOs that need to be completed before merging this PR.
22+
Delete TODOs that do not apply to this PR.
23+
-->
24+
25+
- [ ] Add tests
26+
- [ ] Add entry to changelog
27+
- [ ] Add changes to documentation (guides, repository pages, in-code descriptions)

0 commit comments

Comments
 (0)