public / sequelize

ESDoc failed to build because there were references to the deleted
changelog.md file

- Set up semantic-release to automatically release from CI
- Remove the changelog, which is maintained automatically in GitHub releases from now on
- Add husky git hooks for validating commit messages with validate-commit-msg
- Extend contribution guide
- Adapt GitHub PR template
- Add readme badge

Closes #6550

Small change the docs in order to fix an incorrect ES6 arrow function.

Should reference products instead of projects in "Creating elements of a "HasMany" or "BelongsToMany" association" section.

* drain doesnt take a callback, it returns a promise instead

* update changelog

* add test

* add class method "increment"

Basically moving code from instance method `increment` to class method `increment`.

close #6359

* fix tests. change: require options.where

Column comments are not a currently supported feature and should not possess documentation references.

Documentation should be readded when the feature is supported once again; until then, the documentation is inaccurate and misleading to users.

```
User.findAll({
    where: {
        '$Instruments.name$': { $iLike: '%ooth%' }
    }
    include: [{
        model: Tool,
        as: 'Instruments'
    }]
})
```

Did not have a comma between the key `include` and the key `where`. People who would copy/paste this code would get an error.

A comma was added.

* Create TOC for class methods, cleanup titles

Finding content within the doc is a pain, so adding a link to their sections in the markdown should help. Also styled the class methods in the headings on the page.

* Update models-usage.md

* [ci skip] Docs: Added v3 to v4 migration guide

* Some corrections

* deprecated -> removed

* Extend ES6 class docs

* Fix indentation

* changelog url

* fix: pooling fails to handle disconnection

* fix: memory outage due to leak

* sinon dont like delay, use setTimeout

* review: code refactor

* review: code refactor, get rid of _acquire

* refactor: use race with timeout

* Add relative and full path support for sqlite

If the dialect is 'sqlite', then we parse host+pathname as a file path.
sqlite documentation suggests that this is the right way to parse them:
https://sqlite.org/c3ref/open.html#urifilenameexamples

If the "storage" option is provided, then that wil take precedence.

Examples:
sqlite:subfolder/dbname.db => subfolder/dbname.db
sqlite:/home/abs/dbname.db => /home/abs/dbname.db

* Add dialect check for the unit tests

* Update docs and changelog

* Amplify docs for "import" instruction

Signed-off-by: Martin H. Bramwell <martinhbramwell@gmail.com>

* Uses markdown correctly.  Grammar fixed.

Signed-off-by: Martin H. Bramwell <martinhbramwell@gmail.com>

Introduces dialectOptions.foundRows configuration option that can be set to bring back
update behavior from before this commit https://github.com/sequelize/sequelize/commit/4f95f176eba4a7ad7c71108dd48955884d16eb6b

https://github.com/sequelize/sequelize/issues/7184

* Add `isSoftDeleted` helper method to model instances

Since users can rename the `deletedAt` field when creating a model it
is helpful to have a `isSoftDeleted` so other users of the DB don't
have to hard code the custom `deletedAt` field name throughout their
codebase.

Addresses: https://github.com/sequelize/sequelize/issues/7408

* Update `isSoftDeleted` to check for dates in the future

If the soft-delete property (default is `deleted_at`) is set, but it's
set to a date in the future, then `isSoftDeleted` should return `false`.

* Update `isSoftDeleted` to return `true` if `deletedAt` is now

* Rename variable `isNotSet` to `isSet` and inverse logic

This helps with readability and understanding.

* [MSSQL] Format isolation level as tedious isolation level

* [ci skip] Added changelog entry

* Added unit test that stubs beginTransaction method

* Fixes jshint error

* Explicitly pass tedious lib instance

http://docs.sequelizejs.com/en/v3/docs/getting-started/ link is not active. Thanks

* Indent Markdown by 2 spaces

Consistent with most examples and our codebase

* Use ES6 (as supported by Node 4) in docs

Add Yarn installation scripts to getting started documentation. With many developers making use of Yarn as of late, providing quick copy/paste scripts will prevent developers from having to type the scripts manually.