Issue housekeeping (#2078)

* Added GitHub issue templates and config.yaml for issue templating

* Fixed capitalisation of labels.
This commit is contained in:
Richard 2023-02-17 21:08:59 +00:00 committed by GitHub
parent 5f55ece521
commit 4746eaf5a7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 119 additions and 0 deletions

62
.github/ISSUE_TEMPLATES/bugreport.yaml vendored Normal file
View File

@ -0,0 +1,62 @@
name: Bug Report
description: File a bug report or issue
title: "[Bug]: "
labels: ['Bug', 'triage']
assignees: []
body:
- type: markdown
attributes:
values: >
## Please note:
This form should only be used if _you can reporoduce_ the bug the current
*current* release of netbox. For installation, configuration or other help with Open5GS please
use our [discussion forum](https://github.com/open5gs/open5gs/discussions).
- type: input
attributes:
label: Open5GS Release, Revision, or Tag
placeholder: v2.6.0
validations:
required: true
- type: textarea
attributes:
label: Steps to reproduce
description: >
Please describe in detail the steps needed to reproduce this bug. These steps
should reproduce the issue on the most current release of Open5GS. Be sure to
include configuration and platform details.
Please include logs from the relevant daemons as well as any relevant packet captures.
validations:
required: true
- type: textarea
attributes:
label: Logs
description: Provide any relevant captured logs for the issue
render: shell
- type: textarea
attributes:
label: Expected behaviour
description: What did you expect to happen?
validations:
required: true
- type: textarea
attributes:
label: Observed Behaviour
description: What's the observed behaviour?
validations:
required: true
- type: input
attributes:
label: eNodeB/gNodeB
description: If using an eNB or gNB, please identify which vendor/version
- type: input
attributes:
label: UE Models and versions
description: Which UE hardware model and version or simulator version are you using?

9
.github/ISSUE_TEMPLATES/config.yaml vendored Normal file
View File

@ -0,0 +1,9 @@
blank_issues_enabled: false
contact_links:
- name: Open5GS Contribution Guide
url: https://github.com/open5gs/open5gs/wiki/Contribution-guide
about: Contribution guide detailing how you can help the project
- name: Project Sponsorship
url: https://github.com/sponsors/acetcom
name: Support the Open5GS developer using GitHub sponsorship

View File

@ -0,0 +1,48 @@
name: Feature request
description: Propose an enhancement to Open5GS
labels: ['Enhancement', 'triage']
body:
- type: markdown
attributes:
value: >
## Feature request
Please submit your feature request using the form. If your proposal is not sufficiently
well formed, we may request further clarification and expansion. If you're unsure about
how to formulate your request, please start a [discussion instead](https://github.com/open5gs/open5gs/dicsussions/).
- type: input
attributes:
label: Open5GS Release, Revision, or Tag
placeholder: v2.6.0
validations:
required: true
- type: input
attributes:
label: Components and subsystems
description: Which subsystems and components would this feature be relevant to?
validations:
required: true
- type: textarea
attributes:
label: Proposed functionality
description: >
Provide a detailed description of the feature or behaviour you are proposing. Please include any
Please include any relevant 3GPP standards and references and include any specific changes to
current protocols, processing pipelines, DIAMETER requests/responses, and interfaces. The more detail
you provide, the greater the chance your proposal has of being discussed.
If your feature request does not include anything actionable or sufficient details, you may be asked
to provide further clarification or your request may be rejected.
validations:
required: true
- type: textarea
attributes:
label: External dependencies
description: >
Please detail any new dependencies or implementations that this feature might introduce. e.g. Does the
proposal require the installation of additional packages? Are there further external nodes which may be
required for integration testing? (Not all feature requests will introduce new dependencies)