mirror of
https://gitee.com/dolphinscheduler/DolphinScheduler.git
synced 2024-11-30 03:08:01 +08:00
5855c936a4
* Add label `Waiting for reply` to bug/feature label avoid stale bot close * Remove bot label-on-issue We do not need this anymore, cause when issue is created it would auto add label `waiting for reply` for now * Change issue/pr stale and close days. After this PR merged, issue would be close in 37 days and PR will be close in 127 days.
82 lines
3.0 KiB
YAML
82 lines
3.0 KiB
YAML
#
|
|
# Licensed to the Apache Software Foundation (ASF) under one or more
|
|
# contributor license agreements. See the NOTICE file distributed with
|
|
# this work for additional information regarding copyright ownership.
|
|
# The ASF licenses this file to You under the Apache License, Version 2.0
|
|
# (the "License"); you may not use this file except in compliance with
|
|
# the License. You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
#
|
|
name: Feature request
|
|
description: Suggest an idea for this project
|
|
title: "[Feature][Module Name] Feature title"
|
|
labels: [ "new feature", "Waiting for reply" ]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
For better global communication, Please write in English.
|
|
|
|
If you feel the description in English is not clear, then you can append description in Chinese, thanks!
|
|
|
|
- type: checkboxes
|
|
attributes:
|
|
label: Search before asking
|
|
description: >
|
|
Please make sure to search in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) first
|
|
to see whether the same feature was requested already.
|
|
options:
|
|
- label: >
|
|
I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no
|
|
similar feature requirement.
|
|
required: true
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: Description
|
|
description: A short description of your feature
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: Use case
|
|
description: What do you want to happen?
|
|
placeholder: >
|
|
Rather than telling us how you might implement this feature, try to take a
|
|
step back and describe what you are trying to achieve.
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: Related issues
|
|
description: Is there currently another issue associated with this?
|
|
|
|
- type: checkboxes
|
|
attributes:
|
|
label: Are you willing to submit a PR?
|
|
description: >
|
|
This is absolutely not required, but we are happy to guide you in the contribution process
|
|
especially if you already have a good understanding of how to implement the feature.
|
|
DolphinScheduler is a totally community-driven project and we love to bring new contributors in.
|
|
options:
|
|
- label: Yes I am willing to submit a PR!
|
|
|
|
- type: checkboxes
|
|
attributes:
|
|
label: Code of Conduct
|
|
description: |
|
|
The Code of Conduct helps create a safe space for everyone. We require that everyone agrees to it.
|
|
options:
|
|
- label: |
|
|
I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
|
|
required: true
|
|
|
|
- type: markdown
|
|
attributes:
|
|
value: "Thanks for completing our form!"
|