Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Commit

Permalink
Merge pull request #31 from AtomLinter/update-readme
Browse files Browse the repository at this point in the history
Update the readme
  • Loading branch information
Arcanemagus committed Dec 7, 2015
2 parents e1f8e23 + c7d1403 commit b68c1ac
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 19 deletions.
17 changes: 17 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Contributing

If you would like to contribute enhancements or fixes, please do the following:

1. Fork the plugin repository
2. Hack on a separate topic branch created from the latest `master`
3. Commit and push the topic branch
4. Make a pull request
5. Welcome to the club!

Please note that modifications should follow these coding guidelines:

* Indent is 2 spaces with `.editorconfig`
* Code should pass `eslint` linter
* Vertical whitespace helps readability, don’t be afraid to use it

**Thank you for helping out!**
21 changes: 2 additions & 19 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# linter-js-yaml

This package will lint your `.yaml` opened files in Atom through [js-yaml](https://github.com/connec/yaml-js).
This package will parse your YAML files in Atom through
[js-yaml](https://github.com/connec/yaml-js), exposing any issues reported.

#### Installation

Expand All @@ -21,21 +22,3 @@ You can configure linter-js-yaml by editing ~/.atom/config.cson (choose Open You
```

* `customTags`: List of YAML custom tags. (Default: scalar)

## Contributing

If you would like to contribute enhancements or fixes, please do the following:

1. Fork the plugin repository
2. Hack on a separate topic branch created from the latest `master`
3. Commit and push the topic branch
4. Make a pull request
5. Welcome to the club!

Please note that modifications should follow these coding guidelines:

* Indent is 2 spaces with `.editorconfig`
* Code should pass `eslint` linter with the provided `.eslintrc`
* Vertical whitespace helps readability, don’t be afraid to use it

**Thank you for helping out!**

0 comments on commit b68c1ac

Please sign in to comment.