We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
'
examples like
$ travis-conditions eval "branch = foo" --data '{"branch": "foo"}'
should be like
$ travis-conditions eval 'branch = foo' --data '{"branch": "foo"}'
The reason is that I have for example this:
travis-conditions eval "branch =~ /^release\/(alpha|beta|prod)$/ AND commit_message =~ /\[.*JS.*\]/ AND commit_message !~ /\[.*IOS.*\]/" --data '{"branch": "release/alpha"}'
and as you can see there is !~ in there. This causes the shell to look in the history, resulting in a event not found error.
!~
event not found
Using single quotes instead works as expected.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
examples like
should be like
The reason is that I have for example this:
and as you can see there is
!~
in there. This causes the shell to look in the history, resulting in aevent not found
error.Using single quotes instead works as expected.
The text was updated successfully, but these errors were encountered: