New strategy to trigger release?

[List pull requests associated with commit
](https://developer.github.com/v3/repos/commits/#list-pull-requests-associated-with-commit)

For now, the condition to trigger release is

```
correctCommitMessage && correctBranch
```

(https://github.com/algolia/shipjs/blob/master/packages/shipjs-lib/src/lib/config/defaultConfig.js#L88-L107)

What if it becomes

```
(correctCommitMessage || prLabeled) && correctBranch
```

`prLabeled` here means if the PR associated with the latest commit message has a specific label like "release:trigger".

This might solve issues like #667

Is there any side effect?

Should it become a default behavior? or an opt-in feature?

Start with packages/shipjs-lib/src/lib/config/defaultConfig.js at the referenced condition, then review GitHub’s API for listing pull requests associated with a commit. Trace how release triggering currently uses the commit message and branch, and assess the proposed PR-label path, its side effects, and whether the behavior should be opt-in or default.

Written by the indexing model from the issue text.