Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Templates for issues/pull tracker #99

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
+67 −0
Open

docs: Templates for issues/pull tracker #99

Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
c5478f3
adding pull request template
rpotter12 Aug 16, 2019
186e521
adding issue templates
rpotter12 Aug 16, 2019
2009162
Moved in docs
Aug 18, 2019
22268cc
Added labels and assignees to bug format
Aug 18, 2019
8896ef5
Added title in bug format
Aug 18, 2019
2506f5c
better order of yaml for bug format
Aug 18, 2019
b443096
Removed unnecesary glob
Aug 18, 2019
22d53bc
Improved syntax of bug format
Aug 18, 2019
ffc9f45
Added spaces
Aug 18, 2019
a42e3d8
Requesting verbose informations from end-user for a bug in bug format
Aug 18, 2019
fd62f4b
removed unnecessary spaces
Aug 18, 2019
85562ca
rework of feature request
Aug 18, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 9 additions & 23 deletions docs/feature_request.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,31 +2,17 @@
name: Feature request
about: Suggest an idea for this project

title: "REQUEST: "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As above, when the correct label is applied, I believe prefixing "REQUEST:" to the title adds unneeded distraction.

labels: feature-request "P3 - Normal"
assignees: kreyren nntoan
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having all issues assigned to ya'll may get a bit spamming in your inbox. I'd personally recommend against doing this.

Suggested change
assignees: kreyren nntoan

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR was made by the previous maintainers (they are still maintainers technically, but they became inactive), but I don't have a plan to merge this as is. Maybe I'll pick some parts from this PR someday when I create the templates, but I now don't see the necessity of the templates.

---

**I'm submitting a ...** (check one with "x")
- [ ] bug report
- [x] feature request
### Description/Abstract
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reworked feature request because i think that this is more effective

<!-- Provide short, but verbose explanation about presented feature -->

**Actual Behaviour**

<!-- Describe how the bug manifests. -->
### Expected Behaviour
<!-- Provide Expected behaviour of presented feature -->

**Expected Behaviour**

<!-- State here what the feature should enable the user to do. -->

**Steps to reproduce it**

<!-- Add steps to reproduce bugs or add information on the place where the feature should be implemented. Add links to a sample deployment or code. -->

**System information:**

<!-- Add information about the system your facing this bug on. If you think this is irrelevant or if it's a UI bug or a feature request, please remove this section -->
```
Your operating system
```

**Would you like to work on the issue?**

<!-- Let us know if this issue should be assigned to you or tell us who you think could help to solve this issue. -->
### Actual behaviour (optional)
<!-- Optionally provide actual behaviour of presented feature -->