-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the ability to configure logging levels. #83
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tiate branch names
Prefix slug when PR src and dest branch names are equal
Add failOnNewStates option
Add new E2E options
Add BrowserStack Integration
Add ieNativeEvents option
Support screener-shots
Update to circleci 2.0
Add compareSVGDOM option
…omer-doc Vslt/vslt 367 customer doc
…grate-sc Vslt/vslt 74 integrate sc
Specify Sauce Connect version
The new version of Semaphore changed some of the environment variables. Unfortunately, there's no explicit way to determine if you're using 1.0 or 2.0, so this PR checks for the original variables first, then the 2.0 variables. For Branch information, this PR relies on the 'Workflow ID'. This means that Github status is updated for the same "Branch" across all pipelines in the same Semaphore 2.0 run. From their docs, this seems to most closely match how Semaphore integrates with Github. The alternative would be to use Pipeline ID.
Added details of Semaphore 2.0 support to CHANGELOG.md
Add support for Semaphore 2.0
Current validation will fail for anything other than X.X, but historically `X` and `X.X.X` was supported as well. This reverts the restriction, while maintaining the desired validation. We don't need to update the regex where `launchSauceConnect` is true, because Sauce only supports `X.X`.
…sion Fix browser version validation
@DylanLacey closing this. If needed let us know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes allows the Screener config to accept an
ngrok
object with the keys logFile and logLevel, which are passed through to ngrok.