Skip to content

Commit

Permalink
Adds issue templates
Browse files Browse the repository at this point in the history
  • Loading branch information
gampleman authored Sep 8, 2023
1 parent 15a7152 commit 51f76b6
Show file tree
Hide file tree
Showing 2 changed files with 41 additions and 0 deletions.
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:

**Expected behavior**
A clear and concise description of what you expected to happen.

**Additional context**
Add any other context about the problem here.
21 changes: 21 additions & 0 deletions .github/ISSUE_TEMPLATE/new-function.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
name: New Function
about: Suggest a new function for one of the modules
title: Add ModuleName.Extra.functionName
labels: new function
assignees: ''

---

## `functionName : type -> signature`

<!-- Add suggested documentation here, including some examples with doctests. -->


### Motivating use case

<!-- Why are you proposing this function? In what specific situation did it come in handy? -->

### Rationale

<!-- If this function didn't exist in this library, what would users need to do? Generally speaking if the function you are proposing is an existing function with some minor change (like arguments flipped or a single literal argument pre-applied), you should make a strong argument about the increase in readability or convenience this is going to bring. If it's a more involved function, make an argument about how it can be widely applicable and not just specific to one use case. -->

0 comments on commit 51f76b6

Please sign in to comment.