Configure Travis builds for branches and PRs #67
Merged
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.
Only build master and develop branches when pushed. When a PR is made on GitHub travis will start a build as well.
This change prevents two builds being started for one change, like you can see in PR #61 under "All checks have passed - 2 successful checks".
This PR only triggers one build as you can see below.
Scenario
Steps to reproduce issue
expected result
actual result
New setup
Note
This is the same behavior we have on the Ruby gem repo: appsignal/appsignal-ruby#131