JS File Size Changes (gzipped)

A total of 1 files have changed, with a combined diff of +46 B (+3.1%).

Generated by 🚫 dangerJS against 418ab44

Thank you for contributing @airs0urce!

And for the future: Please don't spam PRs...

Thank you for contributing @airs0urce!

And for the future: Please don't spam PRs...

Thanks!

I was closing PRs after I see tests not passed. If there is way to check tests results before creating PR it would help me to check it before. But I'm not sure if this is possible now.

You can add as many commit as you want, even after creating a PR. The PR will be updated automatically after you push new commits. So if the tests fail, just keep adding commits until they pass.

way to check tests results

If you want to run tests locally, run npm run test. This will run our unit tests.
In your case, the lint failed. This test can be run using npm run lint.

Our CI also runs some additional tests, but the above two are the most important ones.

You can add as many commit as you want, even after creating a PR. The PR will be updated automatically after you push new commits. So if the tests fail, just keep adding commits until they pass.

way to check tests results

If you want to run tests locally, run npm run test. This will run our unit tests. In your case, the lint failed. This test can be run using npm run lint.

Our CI also runs some additional tests, but the above two are the most important ones.

Thank you for the info, will do like that next time. I send PRs not often on github, so didn't get used to the procedure.