From 55c3616e3f6bc88bd810f8953efdc76860fbed9a Mon Sep 17 00:00:00 2001 From: Pierre Vanduynslager Date: Thu, 22 Aug 2019 12:24:32 -0400 Subject: [PATCH] revert: docs(contributing): added instructions on how to run gitbook locally This reverts commit a3da21a54477f8f6c007144e0dd38b800f3caf93. --- CONTRIBUTING.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e6cd5de063..5b560f3767 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,7 +9,6 @@ As a contributor, here are the guidelines we would like you to follow: - [Submitting a Pull Request](#submitting-a-pull-request) - [Coding rules](#coding-rules) - [Working with the code](#working-with-the-code) -- [Working with the doc](#working-with-the-doc) We also recommend that you read [How to Contribute to Open Source](https://opensource.guide/how-to-contribute). @@ -250,10 +249,3 @@ $ npm run test All the [semantic-release](https://github.com/semantic-release) repositories use [Commitizen](https://github.com/commitizen/cz-cli) to help you create [valid commit messages](#commit-message-guidelines). After staging your changes with `git add`, run `npm run cm` to start the interactive commit message CLI. - -## Working with the doc - -Working with the doc is like [working with the code](#working-with-the-code), with the difference that you might find useful to see your changes locally before submitting. - -You can do that by following the instructions on [how to use gitbook locally](https://til.secretgeek.net/gitbook/use_gitbook_locally.html). -