You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cf further discussion in this issue (that happened before this edition, cf original issue text): Currently, we list the repositories that we use in the quality report in a CSV file that has 3 columns: url, to and from. Only url and from are used. We should therefore remove the to column and rename from to commit_hash.
In that repo, one of the files we make predictions for (and actually get errors from) is examples/todos-flow/src/__tests__/reducers/visibilityFilter.test.js.
$ git show 902484ed735d38aec06683c847810a7218d8dba2:examples/todos-flow/src/__tests__/reducers/visibilityFilter.test.js
fatal: Path 'examples/todos-flow/src/__tests__/reducers/visibilityFilter.test.js' does not exist in '902484ed735d38aec06683c847810a7218d8dba2'
Therefore we should not make predictions for it.
The text was updated successfully, but these errors were encountered:
Good point. We should try.
Last time I think about removal it was tricky because it is required to feed two unequal commits to lookout-sdk review call.
The from commit and HEAD should work if I remember correctly. from should also probably be renamed to something like rev since it'll be the only one we'll be using.
cf further discussion in this issue (that happened before this edition, cf original issue text): Currently, we list the repositories that we use in the quality report in a CSV file that has 3 columns:
url
,to
andfrom
. Onlyurl
andfrom
are used. We should therefore remove theto
column and renamefrom
tocommit_hash
.Original issue text
Excerpt from
quality_report_repos.csv
:In that repo, one of the files we make predictions for (and actually get errors from) is
examples/todos-flow/src/__tests__/reducers/visibilityFilter.test.js
.It is present in the
from
revision:but not in the
to
revision:Therefore we should not make predictions for it.
The text was updated successfully, but these errors were encountered: