decrapifier
commented
3 years ago | Fails | |
|---|---|
| :no_entry_sign: | Please assign someone to merge this PR, and optionally include people who should review. |
| :no_entry_sign: | The changelog has not been updated. Please update the changelog. |
| :no_entry_sign: | The version was not updated. Please update the version. |
| Warnings | |
|---|---|
| :warning: | You should add at least 1 more reviewer to the PR |
| :warning: | Branch being merged does not follow [Git Flow](http://nvie.com/posts/a-successful-git-branching-model/) |
| :warning: | The README has not been updated. Please update the README. |
| Messages | |
|---|---|
| :book: | Could not find any browser results. |
| :book: | We were able to automatically fix some formatting issues in this PR for you! |
Some things that were possibly fixed:
- Code that could be fixed via the --fix flag
- Formatting that could be fixed by prettier
Take a look at this commit to see what happened in detail: c67cba94824d852e87a96aaa544290193ff18ca6
And look at this wiki page to see the reasoning behind the ESLint rules: https://github.com/smartprocure/eslint-config-smartprocure/wiki/Rules-and-Why-We-Chose-Them
Generated by :no_entry_sign: dangerJS against d12f20e60ca882bb3c9a89ebcd27fa0d90120d3e
daedalus28
An example of how it might work to kickstart the ticket