2018-09-09 11:24:11 -04:00
|
|
|
<!--
|
2024-02-07 21:54:08 -05:00
|
|
|
Before submitting a PR, please read https://docs.deno.com/runtime/manual/references/contributing
|
2020-10-06 04:40:48 -04:00
|
|
|
|
|
|
|
|
1. Give the PR a descriptive title.
|
|
|
|
|
|
|
|
|
|
Examples of good title:
|
|
|
|
|
- fix(std/http): Fix race condition in server
|
|
|
|
|
- docs(console): Update docstrings
|
|
|
|
|
- feat(doc): Handle nested reexports
|
|
|
|
|
|
|
|
|
|
Examples of bad title:
|
|
|
|
|
- fix #7123
|
|
|
|
|
- update docs
|
|
|
|
|
- fix bugs
|
|
|
|
|
|
|
|
|
|
2. Ensure there is a related issue and it is referenced in the PR text.
|
|
|
|
|
3. Ensure there are tests that cover the changes.
|
|
|
|
|
4. Ensure `cargo test` passes.
|
2020-11-05 09:53:21 -05:00
|
|
|
5. Ensure `./tools/format.js` passes without changing files.
|
|
|
|
|
6. Ensure `./tools/lint.js` passes.
|
2023-01-11 13:44:11 -05:00
|
|
|
7. Open as a draft PR if your work is still in progress. The CI won't run
|
|
|
|
|
all steps, but you can add '[ci]' to a commit message to force it to.
|
2023-01-12 15:45:41 -05:00
|
|
|
8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label.
|
2018-09-09 11:24:11 -04:00
|
|
|
-->
|
