Skip to content

Commit

Permalink
Package's meta update
Browse files Browse the repository at this point in the history
  • Loading branch information
dr-dimitru committed Jan 27, 2018
1 parent 1cbb93b commit 801476f
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
### I'm having an issue:
1. Search [issues](https://github.com/VeliovGroup/Meteor-logger-file/issues?utf8=✓&q=is%3Aissue), maybe your issue is already solved
2. Before submitting an issue make sure it's only related to `ostrio:loggerfile` package
3. If your issue not solved:
3. If your issue is not solved:
- Give an expressive description of what is went wrong
- Version of `ostrio:loggerfile` you're experiencing this issue
- Version of `Meteor` you're experiencing this issue
Expand All @@ -11,17 +11,17 @@
- If you're getting an error or exception, please provide its full stack-trace as plain-text or screenshot

### I have a suggestion:
1. PRs is always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-logger-file/pulls)
2. If you you can not send a PR for some reason:
1. PRs are always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-logger-file/pulls)
2. If you're can not send a PR for some reason:
- Create a new issue ticket
- Describe your feature / request
- How you going to use it? Give a usage example(s)

### Documentation is missing something or incorrect (have typos, etc.):
1. PRs is always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-logger-file/pulls)
2. If you you can not send a PR for some reason:
1. PRs are always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-logger-file/pulls)
2. If you're can not send a PR to docs for some reason:
- Create a new issue ticket
- Give an expressive description what you have changed/added and why
- Make sure you're using correct markdown markup
- Make sure all code blocks starts with tripple ``` (*backtick*) and have a syntax tag, for more read [this docs](https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting)
- Post your addition/changes as issue ticket, we will manage it
- Make sure all code blocks starts with triple ``` (*backtick*) and have a syntax tag, for more read [this docs](https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting)
- Post addition/changes as issue ticket, we will manage it

0 comments on commit 801476f

Please sign in to comment.