This basically brings back the previous behavior we had on Travis CI, where if the commit message included [ci skip], BrowserStack tests didn't run.
Additionally, this allows skipping BrowserStack if the commit message contains [skip ci] too.
This basically brings back the previous behavior we had on Travis CI, where if the commit message included [ci skip], BrowserStack tests didn't run.
Additionally, this allows skipping BrowserStack if the commit message contains [skip ci] too.