Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Remove commit ID field from graphql query fragment #2003

Merged
merged 1 commit into from
Mar 6, 2019

Conversation

kuychaco
Copy link
Contributor

@kuychaco kuychaco commented Mar 6, 2019

This field was not actually being used, and will apparently not be needed for calculating comment positioning any longer.

It also happened to be breaking our PR view due to a dotcom bug (see https://github.com/github/github/issues/109043)

Seems like this won't be needed after all since review comment positions seem to be based on the diff at the time of the query, not the time of the review
@codecov
Copy link

codecov bot commented Mar 6, 2019

Codecov Report

Merging #2003 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2003   +/-   ##
=======================================
  Coverage   92.57%   92.57%           
=======================================
  Files         189      189           
  Lines       11237    11237           
  Branches     1633     1633           
=======================================
  Hits        10403    10403           
  Misses        834      834
Impacted Files Coverage Δ
lib/containers/pr-reviews-container.js 0% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf2abb6...73ba1e4. Read the comment docs.

Copy link
Contributor

@smashwilson smashwilson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@smashwilson smashwilson merged commit 690327e into master Mar 6, 2019
@smashwilson smashwilson deleted the ku-remove-commit-id-field branch March 6, 2019 12:55
@vanessayuenn vanessayuenn mentioned this pull request Mar 6, 2019
9 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants