mirror/netbox-community-netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2024-05-10 07:54:54 +00:00
Code

Issues policy tweaks

Browse Source
This commit is contained in:
jeremystretch
2021-11-05 13:26:18 -04:00
parent e5d7578663
commit 79f2f03fb2
2 changed files with 5 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.github/ISSUE_TEMPLATE/bug_report.yaml vendored
View File

@ -13,10 +13,7 @@ body:
- type: input - type: input
attributes: attributes:
label: NetBox version label: NetBox version
description: > description: What version of NetBox are you currently running?
What version of NetBox are you currently running? (If you don't have access to the most
recent NetBox release, consider testing on our [demo instance](https://demo.netbox.dev/)
before opening a bug report to see if your issue has already been addressed.)
placeholder: v3.0.9 placeholder: v3.0.9
validations: validations:
required: true required: true

12
CONTRIBUTING.md
View File

@ -76,14 +76,10 @@ free to add a comment with any additional justification for the feature.
(However, note that comments with no substance other than a "+1" will be (However, note that comments with no substance other than a "+1" will be
deleted. Please use GitHub's reactions feature to indicate your support.) deleted. Please use GitHub's reactions feature to indicate your support.)
* Due to a large backlog of feature requests, we are not currently accepting * Before filing a new feature request, consider raising your idea in a
any proposals which substantially extend NetBox's functionality beyond its [GitHub discussion](https://github.com/netbox-community/netbox/discussions)
current feature set. This includes the introduction of any new views or models first. Feedback you receive there will help validate and shape the proposed
which have not already been proposed in an existing feature request. feature before filing a formal issue.
* Before filing a new feature request, consider raising your idea on the
mailing list first. Feedback you receive there will help validate and shape the
proposed feature before filing a formal issue.
* Good feature requests are very narrowly defined. Be sure to thoroughly * Good feature requests are very narrowly defined. Be sure to thoroughly
describe the functionality and data model(s) being proposed. The more effort describe the functionality and data model(s) being proposed. The more effort