Skip to content
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

Require static checks to pass in CI #2786

Merged

Conversation

richardsheridan
Copy link
Contributor

Recently the static checks do more than just black and isort. Recent errors like #2783 and #2777 would be caught this way, and it would make it less error prone to rebase some old PRs that lack typing.

Notably this PR won't pass until #2783 and maybe others are fixed. Whenever master shows green on status checks, someone needs to tickle the update and merge buttons.

@codecov
Copy link

codecov bot commented Sep 3, 2023

Codecov Report

Merging #2786 (83671a4) into master (2cd5a6f) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2786   +/-   ##
=======================================
  Coverage   98.94%   98.94%           
=======================================
  Files         113      113           
  Lines       16919    16919           
  Branches     3050     3050           
=======================================
  Hits        16741    16741           
  Misses        123      123           
  Partials       55       55           

Copy link
Contributor

@A5rocks A5rocks left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@richardsheridan
Copy link
Contributor Author

I'll take that approval as permission to self-merge :)

@richardsheridan richardsheridan merged commit 1c15500 into python-trio:master Sep 3, 2023
28 of 29 checks passed
@richardsheridan richardsheridan deleted the require-static-checks branch September 3, 2023 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants