cwinfo/powerdns-admin
5
0
Fork 0
mirror of https://github.com/cwinfo/powerdns-admin.git synced 2024-12-04 11:05:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updating the issue configuration to disable the submission of new issues of all types.

Browse Source
This commit is contained in:
Matt Scott 2023-11-25 08:17:56 -05:00
parent 5d4e560836
commit 17e6adb8a7
No known key found for this signature in database
GPG Key ID: A9A0AFFC0E079001
4 changed files with 0 additions and 215 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

79
.github/ISSUE_TEMPLATE/_bug_report.yaml vendored
View File

@ -1,79 +0,0 @@
---
name: 🐛 Bug Report
description: Report a reproducible bug in the current release of PDA
labels: ["bug / broken-feature"]
body:
- type: markdown
attributes:
value: >
**NOTE:** This form is only for reporting _reproducible bugs_ in a current PDA
installation. If you're having trouble with installation or just looking for
assistance with using PDA, please visit our
[discussion forum](https://github.com/PowerDNS-Admin/PowerDNS-Admin/discussions) instead.
- type: dropdown
attributes:
label: PDA version
description: What version of PDA are you currently running?
options:
- "0.4.1"
- "0.4.0"
- "0.3.0"
- "0.2.5"
- "0.2.4"
- "0.2.3"
- "0.2.2"
- "0.2.1"
- "0.2"
- "0.1"
- "I'm Not Sure"
validations:
required: true
- type: dropdown
attributes:
label: Python version
description: What version of Python are you currently running?
options:
- "3.0"
- "3.1"
- "3.2"
- "3.3"
- "3.4"
- "3.5"
- "3.6"
- "3.7"
- "3.8"
- "3.9"
- "3.10"
- "3.11"
validations:
required: true
- type: textarea
attributes:
label: Steps to Reproduce
description: >
Describe in detail the exact steps that someone else can take to
reproduce this bug using the current stable release of PDA. Begin with the
creation of any necessary database objects and call out every operation being
performed explicitly. If reporting a bug in the REST API, be sure to reconstruct
the raw HTTP request(s) being made. Additionally, **do not rely on the demo instance** for reproducing
suspected bugs, as its data is prone to modification or deletion at any time.
placeholder: |
1. Click on "create widget"
2. Set foo to 12 and bar to G
3. Click the "create" button
validations:
required: true
- type: textarea
attributes:
label: Expected Behavior
description: What did you expect to happen?
placeholder: A new zone record should have been created with the specified values
validations:
required: true
- type: textarea
attributes:
label: Observed Behavior
description: What happened instead?
placeholder: A TypeError exception was raised
validations:
required: true

40
.github/ISSUE_TEMPLATE/_documentation_change.yaml vendored
View File

@ -1,40 +0,0 @@
---
name: 📖 Documentation Change
description: Suggest an addition or modification to the PDA documentation
labels: ["docs / request"]
body:
- type: dropdown
attributes:
label: Change Type
description: What type of change are you proposing?
options:
- Addition
- Correction
- Removal
- Cleanup (formatting, typos, etc.)
validations:
required: true
- type: dropdown
attributes:
label: Area
description: To what section of the documentation does this change primarily pertain?
options:
- Features
- Installation/upgrade
- Getting started
- Configuration
- Customization
- Database Setup
- Debug
- Integrations/API
- Administration
- Development
- Other
validations:
required: true
- type: textarea
attributes:
label: Proposed Changes
description: Describe the proposed changes and why they are necessary.
validations:
required: true

72
.github/ISSUE_TEMPLATE/_feature_request.yaml vendored
View File

@ -1,72 +0,0 @@
---
name: ✨ Feature Request
description: Propose a new PDA feature or enhancement
labels: ["feature / request"]
body:
- type: markdown
attributes:
value: >
**NOTE:** This form is only for submitting well-formed proposals to extend or modify
PDA in some way. If you're trying to solve a problem but can't figure out how, or if
you still need time to work on the details of a proposed new feature, please start a
[discussion](https://github.com/PowerDNS-Admin/PowerDNS-Admin/discussions) instead.
- type: dropdown
attributes:
label: PDA version
description: What version of PDA are you currently running?
options:
- "0.4.1"
- "0.4.0"
- "0.3.0"
- "0.2.5"
- "0.2.4"
- "0.2.3"
- "0.2.2"
- "0.2.1"
- "0.2"
- "0.1"
- "I'm Not Sure"
validations:
required: true
- type: dropdown
attributes:
label: Feature type
options:
- Data model modification
- App Setting Addition
- Default App Setting Change
- New functionality
- Change to existing functionality
validations:
required: true
- type: textarea
attributes:
label: Proposed functionality
description: >
Describe in detail the new feature or behavior you are proposing. Include any specific changes
to work flows, data models, and/or the user interface. The more detail you provide here, the
greater chance your proposal has of being discussed. Feature requests which don't include an
actionable implementation plan will be rejected.
validations:
required: true
- type: textarea
attributes:
label: Use case
description: >
Explain how adding this functionality would benefit PDA users. What need does it address?
validations:
required: true
- type: textarea
attributes:
label: Database changes
description: >
Note any changes to the database schema necessary to support the new feature. For example,
does the proposal require adding a new model or field? (Not all new features require database
changes.)
- type: textarea
attributes:
label: External dependencies
description: >
List any new dependencies on external libraries or services that this new feature would
introduce. For example, does the proposal require the installation of a new Python package?
(Not all new features introduce new dependencies.)

24
.github/ISSUE_TEMPLATE/_housekeeping.yaml vendored
View File

@ -1,24 +0,0 @@
---
name: 🏡 Housekeeping
description: A change pertaining to the codebase itself (developers only)
labels: ["mod / change-request"]
body:
- type: markdown
attributes:
value: >
**NOTE:** This template is for use by maintainers only. Please do not submit
an issue using this template unless you have been specifically asked to do so.
- type: textarea
attributes:
label: Proposed Changes
description: >
Describe in detail the new feature or behavior you'd like to propose.
Include any specific changes to work flows, data models, or the user interface.
validations:
required: true
- type: textarea
attributes:
label: Justification
description: Please provide justification for the proposed change(s).
validations:
required: true