You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix for ParseLambda with itType and resultType: correct order of arguments (#193)
* Fix for ParseLambda with itType and resultType: correct order of arguments
* Add references for missing classes
* Fix for missing classes: UserState and UserProfileDetails
* Small update on unit-test (no need to check for `DoesNotThrow`)
* add comment to appveyor
* Only run SonarScanner on master branch
* APPVEYOR_REPO_BRANCH
* APPVEYOR_PULL_REQUEST_NUMBER
# However, secure variables are not decoded during Pull Request builds which prevents someone from submitting PR with malicious build script displaying those variables. In more controlled environment through with a trusted team and private GitHub repositories there is an option on General tab of project settings to allow secure variables for PRs.
0 commit comments