Skip to content

Commit

Permalink
docs: use correct link to deno doc
Browse files Browse the repository at this point in the history
  • Loading branch information
justinawrey committed Oct 7, 2022
1 parent e3f1ed5 commit 587b493
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,8 @@ tweaks have been made to optimize for Deno:
syncs your code when you publish a Github release, publishing is all you need.

- Documentation changes cause a minor version bump. Documentation is a feature,
especially since [deno doc](https://deno.land/manual/tools/documentation) will
scrape your code. This decision is less of a Deno convention, and mostly my
opinion.
especially since [deno doc](https://doc.deno.land) will scrape your code. This
decision is less of a Deno convention, and mostly my opinion.

- The release workflow is opinionated, and as such runs _fast_ and has _zero
configuration_. `feat!:` will cause a major version bump, `feat:` or `docs:`
Expand Down

0 comments on commit 587b493

Please sign in to comment.