67a222c383
### What this PR does / why we need it?
This patch add the feature branch policy.
After this patch: maintainers are allowed to create a feature branch.
Feature branches are used for collaboration and must include an RFC
link, merge plan and mentor info.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
CI passed
- vLLM version: v0.10.0
- vLLM main:
7be5d113d8
Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
50 lines
1.2 KiB
YAML
50 lines
1.2 KiB
YAML
name: 💬 Request for comments (RFC).
|
|
description: Ask for feedback on major architectural changes or design choices.
|
|
title: "[RFC]: "
|
|
labels: ["RFC"]
|
|
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: >
|
|
#### Please take a look at previous [RFCs](https://github.com/vllm-project/vllm-ascend/issues?q=label%3ARFC+sort%3Aupdated-desc) for reference.
|
|
- type: textarea
|
|
attributes:
|
|
label: Motivation.
|
|
description: >
|
|
The motivation of the RFC.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Proposed Change.
|
|
description: >
|
|
The proposed change of the RFC.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Feedback Period.
|
|
description: >
|
|
The feedback period of the RFC. Usually at least one week.
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
attributes:
|
|
label: CC List.
|
|
description: >
|
|
The list of people you want to CC.
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
attributes:
|
|
label: Any Other Things.
|
|
description: >
|
|
Any other things you would like to mention, such as feature branch request.
|
|
validations:
|
|
required: false
|
|
- type: markdown
|
|
attributes:
|
|
value: >
|
|
Thanks for contributing 🎉!
|