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

chore: use pep621 with hatchling #26

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Wurstnase
Copy link

@Wurstnase Wurstnase commented Jul 1, 2023

@codecov-commenter
Copy link

codecov-commenter commented Jul 2, 2023

Codecov Report

Merging #26 (a29c82f) into master (4d94f64) will not change coverage.
The diff coverage is n/a.

❗ Current head a29c82f differs from pull request most recent head dec0b1b. Consider uploading reports for the commit dec0b1b to get more accurate results

@@            Coverage Diff            @@
##            master       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines           67        61    -6     
  Branches        10        10           
=========================================
- Hits            67        61    -6     

see 3 files with indirect coverage changes

@Wurstnase Wurstnase force-pushed the feat/pep621 branch 2 times, most recently from 966c779 to bf23a11 Compare July 2, 2023 20:41
@aluminum-ice
Copy link

@Wurstnase Nice PR. I've merged it into my fork since I am experimenting with token-bucket and I was looking for something modernized.

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.

3 participants