jshaver
/
ale
forked from github-mirrors/ale
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix markdown headings 

They were all the same size
This commit is contained in:
Adriaan Zonnenberg 2017-04-12 22:26:19 +02:00
parent d2defc8f47
commit 10037c5133
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
CONTRIBUTING.md
View File

@ -13,7 +13,7 @@
<a name="guidelines"></a>
# 1. Guidelines
## 1. Guidelines
Have fun, and work on whatever floats your boat. Take It Easy :tm:.
@ -31,7 +31,7 @@ will check your code while you type.
<a name="issues"></a>
# 2. Creating Issues
## 2. Creating Issues
Before creating any issues, please look through the current list of issues and
pull requests, and ensure that the issue hasn't already been reported. If an
@ -52,7 +52,7 @@ can understand you.
<a name="pull-requests"></a>
# 3. Creating Pull Requests
## 3. Creating Pull Requests
For code you write, make sure to credit yourself at the top of files you add,
and probably those you modify. You can write some comments at the top of your
@ -71,7 +71,7 @@ If you want to credit multiple authors, you can comma separate them.
<a name="adding-a-new-linter"></a>
# 3.i. Adding a New Linter
### 3.i. Adding a New Linter
If you add a new linter, look for existing handlers first in the
[handlers.vim](autoload/ale/handlers.vim) file. One of the handlers there may
@ -87,7 +87,7 @@ alphabetically in the table and list.
<a name="adding-new-options"></a>
# 3.ii. Adding New Options
### 3.ii. Adding New Options
If you add new options to the plugin, make sure to document those new options
in the [README.md](README.md) file, and also in the [help file](doc/ale.txt).
@ -104,7 +104,7 @@ easy to see what the default is with `:echo g:ale...`.
<a name="writing-documentation"></a>
# 4. Writing Documentation
## 4. Writing Documentation
If you are adding new linters, changing the API, adding new options, etc., you
_must_ write some documentation describing it in the `doc/ale.txt` file. New
@ -113,7 +113,7 @@ quick overview of the supported tools.
<a name="documenting-new-linters"></a>
# 4.i Documenting New Linters
### 4.i Documenting New Linters
If you add a new linter to the project, edit the table in the `README.md` file,
and edit the list of linters at the top of the `doc/ale.txt` file. The linters
@ -125,7 +125,7 @@ giving some unfair preference to any particular tool or language.
<a name="editing-online-documentation"></a>
# 4.ii Editing the Online Documentation
### 4.ii Editing the Online Documentation
The "online documentation" file used for this project lives in `doc/ale.txt`.
This is the file used for generating `:help` text inside Vim itself. There are
@ -145,7 +145,7 @@ some guidlines to follow for this file.
<a name="documenting-linter-options"></a>
# 4.iii Documenting Linter Options
### 4.iii Documenting Linter Options
For documenting new linter options, please add a new sub-section under the
"Linter Specific Options" section describing all of the global options added
@ -155,7 +155,7 @@ to look up the default value easily by typing `:echo g:ale_...`.
<a name="in-case-of-busses"></a>
# 5. In Case of Busses
## 5. In Case of Busses
Should the principal author of the ALE project and all collaborators with the
required access needed to properly administrate the project on GitHub or any