CI: silence codecov for unrelated lines

[erfannariman]

No description provided.

[jbrockmendel]

I guess to check that this works we'll need to merge it and then see if subsequent PRs stop showing the unwanted comments?

[erfannariman]

@jbrockmendel yes I think so. Checking codecov for this PR was not very informative.

[codecov]

Codecov Report

Merging #36600 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #36600      +/-   ##
==========================================
- Coverage   94.20%   94.19%   -0.01%     
==========================================
  Files         212      212              
  Lines       50332    50340       +8     
==========================================
+ Hits        47414    47418       +4     
- Misses       2918     2922       +4     

Impacted Files	Coverage Δ
pandas/io/gbq.py	88.88% <0.00%> (-11.12%)	⬇️
pandas/core/frame.py	97.44% <0.00%> (-0.12%)	⬇️
pandas/core/indexes/base.py	98.61% <0.00%> (+<0.01%)	⬆️

---

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 0f6fc8d...d9149fb. Read the comment docs.

[erfannariman]

@jbrockmendel seems to work :)

[jorisvandenbossche]

@erfannariman what change in this PR would "silence codecov for unrelated lines" (as the title indicates?)

[erfannariman]

@erfannariman what change in this PR would "silence codecov for unrelated lines" (as the title indicates?)

Might have misunderstood initially if I read the comments under this PR. I thought we only wanted codecov for the lines which is touched by a PR, and ignore the rest, that's why I named it like this.

[jorisvandenbossche]

I thought we only wanted codecov for the lines which is touched by a PR, and ignore the rest, that's why I named it like this.

Yes, but so the issue what (I thought) we were talking about is the fact that there were "annotations" (inline code comments in the "files changed" tab) about unrelated files, which is something alse as a normal comment on a PR. So therefore I didn't see the link between the changes you did and the problem.
Now, I can't directly find an example PR where there are a lot of those spurious annotations, so maybe the problem has already solved itself .. (@dsaxton do you still see an example somewhere?)

[dsaxton]

Now, I can't directly find an example PR where there are a lot of those spurious annotations, so maybe the problem has already solved itself .. (@dsaxton do you still see an example somewhere?)

Hmm, I can't seem to find one either. Maybe it was fixed upstream?

[jorisvandenbossche]

Example in an older PR: https://github.com/pandas-dev/pandas/pull/36434/files

[erfannariman]

This looks already solved then. Should I close this?

[dsaxton]

This looks already solved then. Should I close this?

Could also give it a few days to see if any pop up? My guess is they fixed the behavior upstream (it was in "beta" after all), but doesn't hurt to wait and see.

[dsaxton]

Found one 😄 (this one just opened)

https://github.com/pandas-dev/pandas/pull/36706/files

Edit: Another one: https://github.com/pandas-dev/pandas/pull/36716/files

I think making this change can't hurt, although I think we should be modifying the github_checks section.

[erfannariman]

is this what you meant @dsaxton ?

The codecov report is updated after every commit, see here in the edits.

[dsaxton]

is this what you meant @dsaxton ?

The codecov report is updated after every commit, see here in the edits.

Yeah I believe that should work, although I think we also don't want the Codecov comments according to #36600 (comment)

[erfannariman]

is this what you meant @dsaxton ?
The codecov report is updated after every commit, see here in the edits.

Yeah I believe that should work, although I think we also don't want the Codecov comments according to #36600 (comment)

Removed comments

[dsaxton]

Git is complaining about no EOF new line, but otherwise looks good, thanks @erfannariman

[MarcoGorelli]

Git is complaining about no EOF new line, but otherwise looks good, thanks @erfannariman

there's a pre-commit hook for that ;) https://github.com/pre-commit/pre-commit-hooks (end-of-file-fixer)

[dsaxton]

there's a pre-commit hook for that ;) https://github.com/pre-commit/pre-commit-hooks (end-of-file-fixer)

Very cool, we might as well use it IMO

[jreback]

ok if you'd fix the EOF issue can merge (and yes good idea to add to the pre-commit hook / separate PR pls)

[erfannariman]

ok if you'd fix the EOF issue can merge (and yes good idea to add to the pre-commit hook / separate PR pls)

ready

[erfannariman]

@dsaxton I changed comment: off to comment: false as stated in the docs

[dsaxton]

Thanks @erfannariman I think this is working. Had some unrelated annotations on a PR, merged master and they disappeared.