Repository navigation
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably good to remove the branch filter. I usually have every branch build on
push.I don't normally bother with
pull_requestbuilds. They don't tend to be super useful if there is only a single development branch open at any given time, or only one developer actively working on a project. Assuming nothing has been merged to the base branch since the current branch was opened (or last rebased), a PR build won't really differ from a branch build. Additionally the PR builds don't start until a PR is opened, which means you have to wait for builds after opening a PR, whereas branch builds start earlier and are often done by the time a PR is opened.Edit:
Also, when there are multiple branches open or multiple active developers on a project, PR builds tend to become stale anyway, especially if review takes awhile. I find rebasing a branch and relying on branch builds to be more reliable.