-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Use travis-provided branch range as commit base, where possible #4821
Conversation
Firefox (nightly channel)Testing revision 3eaa1d7 All results/dom/historical.html
|
Chrome (unstable channel)Testing revision 3eaa1d7 All results/dom/historical.html
|
c7386a3
to
7264826
Compare
r? @bobholt |
This fixes a problem where PRs not against master included all the commits in their branch in the stability check, rather than just the changes since the base branch.
No one looks at the results and it's mostly redundant with the stability checker output.
Thanks, James! |
These tests are now available on w3c-test.org |
@bobholt Above, the bot appears to have built this branch in response to the merge event. My guess is that it is subscribed to one event too many. Whatever the case, I think you'll agree that this inefficiency is pretty low-priority. Just wanted to give you a heads-up! |
No description provided.