8000 update PR template · vuejs/rfcs@6088917 · GitHub
[go: up one dir, main page]
Skip to content

Commit 6088917

Browse files
yyx990803yyx990803
committed
update PR template
1 parent e319c82 commit 6088917

File tree

2 files changed

+30
-6
lines changed

2 files changed

+30
-6
lines changed

‎.github/pull_request_template.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
## Summary
2+
3+
<!--
4+
Short summary on what problem this RFC solves, and
5+
concise example usage of the feature
6+
-->
7+
8+
## Links
9+
10+
<!--
11+
Link to a GitHub-rendered version of your RFC, e.g.
12+
https://github.com/<USERNAME>/rfcs/blob/<BRANCH>/active-rfcs/0000-my-proposal.md
13+
You can find this link by navigating to this file on your branch.
14+
-->
15+
- [Full Rendered Proposal]()
16+
17+
<!--
18+
Please open and link to a corresponding discussion thread (under "Discussion" tab of the repo). Make sure to:
19+
- Reference PR #id in its title.
20+
- Link to this RFC in its body.
21+
-->
22+
- [Discussion Thread]()
23+
24+
<!-- include additional links to related issues if applicable -->
25+
26+
---
27+
28+
**Important: Do NOT comment on this PR. Please use the discussion thread linked above to provide feedback, as it provides branched discussions that are easier to follow. This also makes the edit history of the PR clearer.**

‎README.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -85,13 +85,9 @@ present convincing motivation, demonstrate understanding of the
8585
impact of the design, or are disingenuous about the drawbacks or
8686
alternatives tend to be poorly-received**.
8787

88-
* Submit a pull request. As a pull request the RFC will receive design
89-
feedback from the larger community, and the author should be prepared
90-
to revise it in response.
88+
* Submit a pull request. Make sure to follow the pull request template and open a corresponding discussion thread.
9189

92-
* Build consensus and integrate feedback. RFCs that have broad support
93-
are much more likely to make progress than those that don't receive any
94-
comments.
90+
* Build consensus and integrate feedback in the discussion thread. RFCs that have broad support are much more likely to make progress than those that don't receive any comments.
9591

9692
* Eventually, the [core team] will decide whether the RFC is a candidate
9793
for inclusion in Vue.

0 commit comments

Comments
 (0)
0