Adds rfc template #316
Merged
Adds rfc template #316
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Consider issue templates |
|
I'm not exactly sure how issue templates work, but from what I gather the text in the ISSUE_TEMPLATE is inserted into every new issue. If that's right, I'd prefer to leave it in a standalone file for now since I'd like to reserve rfcs for big stuff. |
|
Right, but you don't have to insert the entire RFC template in the issue template, you can just point folks to it during issue creation behind HTML comment tags (so they don't show up in the actual issue). So, for example, something like this: And so on... |
|
Ah, got ya. |
|
Got the issue template in: #317 |
tizmagik
added a commit
that referenced
this pull request
Dec 14, 2016
* master: (35 commits) creates local copies of packages so e2e tests use latest code (#345) adds style and script linter packages (#344) now using npm version to check for kyt-cli updates (#337) Adds kyt version option to setup command (#343) make lint-script command; lint now runs scripts and style (#339) Adds bootstrap scripts (#341) fixes test coverage command (#342) Run test from root directory (#336) Monorepo (#330) [ci skip] document Jest/Watchman issue and common workaround (#334) Catch SIGINT (#332) Fixes e2e tests (#326) Removes deprecated reflect eslint rule (#325) Upgrade Linter dependencies (#289) [doc]fix path of eslintrc and stylelintrc (#321) Update unit tests for changes made to resolve #303 (#318) adds ISSUE_TEMPLATE (#317) Adds rfc template (#316) document possible kyt setup repository url formats (#314) Overwrites default npm init test script on setup (#293) ... # Conflicts: # .travis.yml # e2e_tests/tests/cli.test.js # package.json # packages/kyt-cli/cli/actions/setup.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're testing a new rfc process in github Issues. So far the idea is to copy and use the rfc template from the Rust repository. We plan on working out the details for the process - how are rfcs labeled, what are their various stages, how are they accepted - as we roll out the first couple proposals.
Feel free to leave ideas here about the initial rfc process. I'll open an Issue so that we can further discuss the final process.