Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moves contributing to separate file #95

Merged
merged 2 commits into from
Oct 29, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
Check the [issue tracker](https://github.com/microplan-xyz/microplan/issues) for all work in progress. Before sending a PR or adding a new feature, please take time to open an issue and begin a discussion about it.

If you are sending a PR, make sure to change the version in package.json according to your changes. You can use the `npm version` command to achieve this

```bash
$ npm version patch # for bug fixes
$ npm version minor # for new features
$ npm version major # for deprecation
```

**Important:** `microplan` uses an automated publishing system. That means whenever your PR is merged, `microplan` will be published automatically to npm (based on the version specified in the package.json)
19 changes: 2 additions & 17 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -189,25 +189,10 @@ The configuration file can be written in various formats. We plan to add TOML so
| JSON | AVAILABLE |
| TOML | PLANNED |


## Contributing
Check the [issue tracker](https://github.com/microplan-xyz/microplan/issues) for all work in progress. Before sending a PR or adding a new feature, please take time to open an issue and begin a discussion about it.

If you are sending a PR, make sure to change the version in package.json according to your changes. You can use the `npm version` command to achieve this

```bash
$ npm version patch # for bug fixes
$ npm version minor # for new features
$ npm version major # for deprecation
```

**Important:** `microplan` uses an automated publishing system. That means whenever your PR is merged, `microplan` will be published automatically to npm (based on the version specified in the package.json)

## Contributors
### Contributors
Authored and maintained by [@scriptnull](https://github.com/scriptnull) and [@argonlaser](https://github.com/argonlaser) with help from [contributors](http://github.com/microplan-xyz/microplan/contributors).

## Attributions

### Attributions
Thanks to the awesome repositories without which the project would not have been possible.

```js
Expand Down