ci(upstream): run against latest html5lib-tests master #2288
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
flavorjones
force-pushed
the
flavorjones-upstream-html5lib-tests
branch
2 times, most recently
from
129bdde
to
9ea9c10
Compare
flavorjones
force-pushed
the
flavorjones-upstream-html5lib-tests
branch
from
9ea9c10
to
ca05768
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What problem is this PR intended to solve?
As the
html5lib-testsrepo changes over time, I think it might be helpful to automatically run against the latest so that if any failures are introduced, we can address them proactively.This PR adds a job to the
upstreamCI pipeline, which runs periodically every few days, running against the latest versions of some of Nokogiri's dependencies.I'll rely on @stevecheckoway to tell me if this is actually useful.
Have you included adequate test coverage?
This PR introduces new test coverage.
Does this change affect the behavior of either the C or the Java implementations?
No functional changes.