Allow pre-filled GitHub issue forms via links (#19925)

Closes #19924
This commit is contained in:
Alexander Schwartz 2023-04-25 12:52:17 +02:00 committed by GitHub
parent 30d976d64c
commit e21fc968e2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 19 additions and 0 deletions

View file

@ -55,36 +55,42 @@ body:
validations:
required: true
- type: textarea
id: description
attributes:
label: Describe the bug
description: Provide a clear and concise description of what the problem is.
validations:
required: true
- type: input
id: version
attributes:
label: Version
description: What version of Keycloak are you running?
validations:
required: true
- type: textarea
id: behaviorExpected
attributes:
label: Expected behavior
description: Describe the expected behavior clearly and concisely.
validations:
required: true
- type: textarea
id: behaviorActual
attributes:
label: Actual behavior
description: Describe the actual behavior clearly and concisely.
validations:
required: true
- type: textarea
id: reproducer
attributes:
label: How to Reproduce?
description: Provide clear and concise steps to reproduce the problem.
validations:
required: true
- type: textarea
id: other
attributes:
label: Anything else?
description: Links? References? Anything that will give us more context about the issue you are encountering!

View file

@ -3,12 +3,14 @@ description: Request an enhancement to an existing feature
labels: ["kind/enhancement", "status/triage"]
body:
- type: textarea
id: description
attributes:
label: Description
description: Describe the enhancement at a high-level.
validations:
required: true
- type: input
id: discussion
attributes:
label: Discussion
description: |
@ -18,12 +20,14 @@ body:
validations:
required: false
- type: textarea
id: motivation
attributes:
label: Motivation
description: Describe why the feature should be added.
validations:
required: false
- type: textarea
id: details
attributes:
label: Details
description: More details? Implementation ideas? Anything that will give us more context about the enhancement you are proposing!

View file

@ -3,12 +3,14 @@ description: A large feature that is broken down into multiple linked issues.
labels: ["kind/epic", "status/triage"]
body:
- type: textarea
id: description
attributes:
label: Description
description: Describe the feature at a high-level.
validations:
required: true
- type: input
id: discussion
attributes:
label: Discussion
description: |
@ -16,6 +18,7 @@ body:
validations:
required: true
- type: textarea
id: issues
attributes:
label: Issues
description: List the issues related to this epic.
@ -25,6 +28,7 @@ body:
validations:
required: false
- type: textarea
id: motivation
attributes:
label: Motivation
description: Provide a brief explanation of why the feature should be added.

View file

@ -3,12 +3,14 @@ description: Request a new feature to be added to Keycloak
labels: ["kind/feature", "status/triage"]
body:
- type: textarea
id: description
attributes:
label: Description
description: Describe the feature at a high-level.
validations:
required: true
- type: input
id: discussion
attributes:
label: Discussion
description: |
@ -18,12 +20,14 @@ body:
validations:
required: false
- type: textarea
id: motivation
attributes:
label: Motivation
description: Describe why the feature should be added.
validations:
required: false
- type: textarea
id: details
attributes:
label: Details
description: Design ideas? Implementation ideas? Anything that will give us more context about the feature you are proposing!

View file

@ -3,6 +3,7 @@ description: Any tasks that are not directly adding a new feature, enhancement o
labels: ["kind/task"]
body:
- type: textarea
id: description
attributes:
label: Description
description: Describe the task.