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.
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
Checks: Plumb channel and improve robustness of diff urls #889
Checks: Plumb channel and improve robustness of diff urls #889
Changes from 5 commits
11c467c
038de5e
87a5328
9688cdf
e87d399
69d2ccf
20d2bc1
b69bd8e
eaa1dcf
95eea8f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This is probably not specific enough in some cases.
Example: when
headRun
is a PR run, we would only passbrowser[channel]@revision
toGetMasterDiffURL
, which will match to bothpr_base
andpr_head
runs, and the users would always expect thepr_head
run.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.
This is deliberately the case. This only needs to identify any runs precisely enough for a given check; i.e. the CheckState's product is specific enough to identify chrome[experimental], and what the means as a check depends on what's been run (e.g.
master
vs an earliermaster
,pr_base
vspr_head
, etc.)As for below, let's rejig the API to take a run to diff against master, and then we can be less ambiguous :)
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.