From f32ee4af485a0e32d71c17c3a62aa390156e6dbf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcel=20St=C3=B6r?= Date: Fri, 6 Nov 2015 00:55:14 +0100 Subject: [PATCH] Fix TOC --- CONTRIBUTING.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cd995a17..645ee3a4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -11,12 +11,8 @@ The following is a set of guidelines for contributing to NodeMCU on GitHub. Thes [Development environment setup](#development-environment-setup) [Working with Git and GitHub](#working-with-git-and-github) - * [Submitting Issues](#submitting-issues) - * [Your First Code Contribution](#your-first-code-contribution) - * [Pull Requests](#pull-requests) - -[Styleguides](#styleguides) * [General flow](#general-flow) + * [Keeping your fork in sync](#keeping-your-fork-in-sync) * [Commit messages](#commit-messages) ## Development environment setup @@ -75,4 +71,4 @@ Further paragraphs come after blank lines. Don't forget to [reference affected issues](https://help.github.com/articles/closing-issues-via-commit-messages/) in the commit message to have them closed automatically on GitHub. -[Amend](https://help.github.com/articles/changing-a-commit-message/) your commit messages if necessary to make sure what the world sees on GitHub is as expressive and meaningful as possible. \ No newline at end of file +[Amend](https://help.github.com/articles/changing-a-commit-message/) your commit messages if necessary to make sure what the world sees on GitHub is as expressive and meaningful as possible.