Skip to content

Commit

Permalink
chore: tweak issue/pr templates
Browse files Browse the repository at this point in the history
  • Loading branch information
egoist committed Sep 10, 2019
1 parent 45d352c commit a56011e
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 23 deletions.
8 changes: 0 additions & 8 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,26 +1,18 @@
---
name: Bug report
about: Create a report to help us improve

---

<!-- Please don't delete this template or we'll close your issue -->
<!-- Before creating an issue please make sure you are using the latest version of Saber. -->

<!-- Please confirm you will submit an issue. -->
<!-- Issues which contain questions or support requests will be closed. -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

- [ ] I confirm that this is an issue rather than a question.

<!-- Please ask questions via following several ways. -->
<!-- https://chat.saber.land/ -->
<!-- https://stackoverflow.com/questions/ask?tags=saberjs -->

## Bug report

#### Version

#### Steps to reproduce

<!-- If you are reporting a bug that can ONLY be reproduced on your repository, PLEASE provide this repo link. That takes guessing work out of the way and saves us time. -->
Expand Down
19 changes: 4 additions & 15 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@

**Summary**

<!-- If this PR fixes certain issues -->
<!-- You can use the `Closes #issue_number` syntax here to close them -->

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
Expand All @@ -26,21 +29,7 @@ If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

- [ ] Chrome
- [ ] Firefox
- [ ] Safari
- [ ] Edge
- [ ] IE

If adding a **new feature**, the PR's description includes:

- [ ] A convincing reason for adding this feature
- [ ] Related documents have been updated
- [ ] Related tests have been updated
- [ ] Briefly describing what this PR does in the title in [Angular Commit Message Conventions](https://git.io/fNGDG), e.g. `fix: rebuild when a page is added`

To avoid wasting your time, it's best to open a **feature request issue** first and wait for approval before working on it.

Expand Down

0 comments on commit a56011e

Please sign in to comment.