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

Setup our CI for a merge queue #3147

Merged
merged 1 commit into from
Dec 8, 2024
Merged

Conversation

A5rocks
Copy link
Contributor

@A5rocks A5rocks commented Dec 3, 2024

Step one of having a merge queue for trio, I think. Couldn't find any good references to check against.

@A5rocks A5rocks changed the title Run our GitHub actions on the merge queue Setup our CI for a merge queue Dec 3, 2024
Copy link

codecov bot commented Dec 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.62%. Comparing base (f9411f4) to head (3b8bdec).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3147   +/-   ##
=======================================
  Coverage   99.62%   99.62%           
=======================================
  Files         122      122           
  Lines       18396    18396           
  Branches     1222     1222           
=======================================
  Hits        18327    18327           
  Misses         47       47           
  Partials       22       22           

@A5rocks A5rocks merged commit da89ae8 into python-trio:main Dec 8, 2024
38 checks passed
@A5rocks A5rocks deleted the mergegroup-actions branch December 8, 2024 02:42
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.

2 participants