Skip to content

Backport #17606 to v3.2.x #17611

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 11, 2020
Merged

Backport #17606 to v3.2.x #17611

merged 1 commit into from
Jun 11, 2020

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Jun 10, 2020 •
edited
Loading

PR Summary

Oddly, we don't seem to use -y on this branch, so I'm not sure if codecov was just doing whatever its default was on this branch.

Backport of #17606.

PR Checklist

  • [N/A] Has Pytest style unit tests
  • [N/A] Code is Flake 8 compliant
  • [N/A] New features are documented, with examples if plot related
  • [N/A] Documentation is sphinx and numpydoc compliant
  • [N/A] Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • [N/A] Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

@QuLogic
Move codecov.yml to .github.
904f87f 
Then removing the `-y` argument to the script fixes a deprecation
warning from it.
@QuLogic QuLogic added this to the v3.2.2 milestone Jun 10, 2020
@tacaswell tacaswell merged commit 56270eb into matplotlib:v3.2.x Jun 11, 2020
@QuLogic QuLogic deleted the codecov-warnings branch June 11, 2020 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
topic: testing
Projects
None yet
Milestone
v3.2.2
Development

Successfully merging this pull request may close these issues.
2 participants
@QuLogic @tacaswell