db-migrate
Advanced tools
db-migrate - npm Package Compare versions
Comparing version 0.10.5 to 0.10.6
@@ -0,1 +1,19 @@ | ||
| <a name="0.10.6"></a> | ||
| ## [0.10.6](https://github.com/db-migrate/node-db-migrate/compare/v0.10.5...v0.10.6) (2018-03-21) | ||
| ### Bug Fixes | ||
| * **ci:** add ignores for backported features ([53dedc2](https://github.com/db-migrate/node-db-migrate/commit/53dedc2)) | ||
| ### Features | ||
| * **contribution:** enrich contribution instructions ([93b5cea](https://github.com/db-migrate/node-db-migrate/commit/93b5cea)), closes [#549](https://github.com/db-migrate/node-db-migrate/issues/549) | ||
| * **contribution:** enrich contribution instructions, issues ([d87a734](https://github.com/db-migrate/node-db-migrate/commit/d87a734)) | ||
| * **progamableApi:** CMD options can be passed programatically now ([69d7605](https://github.com/db-migrate/node-db-migrate/commit/69d7605)) | ||
| * **progamableApi:** using const now ([a69e221](https://github.com/db-migrate/node-db-migrate/commit/a69e221)) | ||
| <a name="0.10.4"></a> | ||
@@ -2,0 +20,0 @@ ## [0.10.4](https://github.com/db-migrate/node-db-migrate/compare/v0.10.3...v0.10.4) (2018-02-06) |
@@ -0,1 +1,38 @@ | ||
| # Contributing by opening an Issue or Discussing | ||
| Whenever you find a bug, which you do not have the time to fix, it is still important | ||
| to get your input. Same goes for feature suggestions and everything else that helps | ||
| a project to get better. | ||
| Here are a few points to consider before creating an issue or discussing within one: | ||
| 1. Make sure you have proper description of your problem or what exactly you want: | ||
| We have issue templates in place that should help you with this one and this is really | ||
| important, since we may not just agree with you, if we don't understand your use case. | ||
| 2. Be constructive and before you post think once more if this is going to waste the maintainers | ||
| time, or if it is going to actually help them. | ||
| Since being constructive, is a big vague, here some simple points that should help you: | ||
| 2.1. Just stating something is wrong, is not constructive. | ||
| When you've got the feeling something is wrong, try to understand first if it is really wrong | ||
| and if it is make suggestions on how to improve, or even better open a PR and make the open source | ||
| world once again even better! | ||
| 2.2. "Does not work", is not a proper problem description | ||
| Neither is, "see title". When you follow the issue template and provide all informations asked for | ||
| you should be pretty fine, in providing us exactly the information we need to help you. | ||
| 2.3. Follow the CoC and contribute, not attack | ||
| An example when you're not contributing, but attacking is, should you just impose you're right | ||
| and you should be followed. It is always about the dialogue, that makes the difference. After all | ||
| you should be fine, by just using your common sense. | ||
| # Contributing a Pull Request | ||
| Without pull requests from generous people like you, this project | ||
@@ -11,13 +48,18 @@ wouldn't be what it is today. You are planning to contribute aren't you? | ||
| 3. Run the tests. Pull requests without tests are much less likely to be | ||
| merged, and it's great to know you're starting with a clean slate: `npm test`. | ||
| Be sure to check the README for setting up your test databases first. | ||
| merged, and it's great to know you're starting with a clean slate: `npm test`. | ||
| Be sure to check the README for setting up your test databases first. | ||
| 4. Add a test for your change. Refactoring and documentation changes | ||
| require no new tests. If you are adding functionality or fixing a bug, | ||
| please include a test. | ||
| require no new tests. If you are adding functionality or fixing a bug, | ||
| please include a test. | ||
| 5. Make the test pass. | ||
| 6. Push to your fork and submit a pull request. | ||
| 6. Create a commit that complies with our conventions, which you can view | ||
| [here](https://github.com/conventional-changelog/conventional-changelog/tree/35e60b5be6027fb2784c5103eee111f6f99b045e/packages/conventional-changelog-angular) | ||
| and last but not least also comply to the [DCO](https://github.com/probot/dco#how-it-works). | ||
| Which easiest work with just commiting via `git commit -s -m 'your commit message'`. | ||
| 7. Push to your fork and submit a pull request. | ||
| At this point you're waiting on me. In a perfect world I'd commit to | ||
@@ -24,0 +66,0 @@ responding to your request in some short period of time. Unfortunately, |
@@ -101,5 +101,6 @@ var optimist = require('optimist'); | ||
| } else { | ||
| const _internalsArgv = Object.assign(defaultConfig, internals.cmdOptions); | ||
| internals.argv = { | ||
| get argv () { | ||
| return defaultConfig; | ||
| return _internalsArgv; | ||
| } | ||
@@ -106,0 +107,0 @@ }; |
@@ -34,3 +34,3 @@ { | ||
| ], | ||
| "version": "0.10.5", | ||
| "version": "0.10.6", | ||
| "engines": { | ||
@@ -51,3 +51,3 @@ "node": ">=0.6.0" | ||
| "db-migrate-shared": "^1.1.2", | ||
| "deep-extend": "^0.4.1", | ||
| "deep-extend": "^0.5.0", | ||
| "dotenv": "^2.0.0", | ||
@@ -69,3 +69,3 @@ "final-fs": "^1.6.0", | ||
| "db-migrate-base": "^1.2.5", | ||
| "db-migrate-mysql": "^1.1.7", | ||
| "db-migrate-mysql": "^1.1.10", | ||
| "db-migrate-sqlite3": "^0.2.1", | ||
@@ -72,0 +72,0 @@ "eslint": "^4.10.0", |
Sorry, the diff of this file is not supported yet
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by3.42%
131348
- Number of package files
- increased by1.82%
56
- Lines of code
- increased by1.27%
3435
Dependency changes
+ Addeddeep-extend@0.5.1(transitive)
- Removeddeep-extend@0.4.2(transitive)
Updateddeep-extend@^0.5.0