summaryrefslogtreecommitdiff
path: root/std/README.md
diff options
context:
space:
mode:
authorRyan Dahl <ry@tinyclouds.org>2019-10-09 17:22:22 -0400
committerRyan Dahl <ry@tinyclouds.org>2019-10-09 17:22:22 -0400
commit93f7f00c956c14620ef031626f124b57397ca867 (patch)
treec5a9f536e79d2c8d2d02897511a9138acaf35394 /std/README.md
parent28293acd9c12a94f5d769706291032e844c7b92b (diff)
Run deno_std tests in github actions
Diffstat (limited to 'std/README.md')
-rw-r--r--std/README.md14
1 files changed, 6 insertions, 8 deletions
diff --git a/std/README.md b/std/README.md
index 5e2cbf044..ee9c408df 100644
--- a/std/README.md
+++ b/std/README.md
@@ -1,7 +1,5 @@
# Deno Standard Modules
-[![Build Status](https://dev.azure.com/denoland/deno_std/_apis/build/status/denoland.deno_std?branchName=master)](https://dev.azure.com/denoland/deno_std/_build/latest?definitionId=2?branchName=master)
-
These modules do not have external dependencies and they are reviewed by the
Deno core team. The intention is to have a standard set of high quality code
that all Deno projects can use fearlessly.
@@ -11,8 +9,8 @@ Contributions are welcome!
## How to use
These modules are tagged in accordance with Deno releases. So, for example, the
-v0.3.0 tag is guaranteed to work with deno v0.3.0.
-You can link to v0.3.0 using the URL `https://deno.land/std@v0.3.0/`
+v0.3.0 tag is guaranteed to work with deno v0.3.0. You can link to v0.3.0 using
+the URL `https://deno.land/std@v0.3.0/`
It's strongly recommended that you link to tagged releases rather than the
master branch. The project is still young and we expect disruptive renames in
@@ -40,10 +38,10 @@ Here are the dedicated documentations of modules:
## Contributing
deno_std is a loose port of [Go's standard library](https://golang.org/pkg/).
-When in doubt, simply port Go's source code, documentation, and tests. There
-are many times when the nature of JavaScript, TypeScript, or Deno itself
-justifies diverging from Go, but if possible we want to leverage the energy that
-went into building Go. We generally welcome direct ports of Go's code.
+When in doubt, simply port Go's source code, documentation, and tests. There are
+many times when the nature of JavaScript, TypeScript, or Deno itself justifies
+diverging from Go, but if possible we want to leverage the energy that went into
+building Go. We generally welcome direct ports of Go's code.
Please ensure the copyright headers cite the code's origin.