Closed pepoluan closed 1 year ago
Why is the CI not triggered
Edit: Duh it does not trigger on changes to README.rst. Pushing another commit to trigger it.
Merging #326 (8bb1551) into master (c78fc95) will not change coverage. The diff coverage is
100.00%
.
@@ Coverage Diff @@
## master #326 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 7 7
Lines 1691 1696 +5
Branches 314 310 -4
=========================================
+ Hits 1691 1696 +5
Impacted Files | Coverage Δ | |
---|---|---|
aiosmtpd/smtp.py | 100.00% <100.00%> (ø) |
|
aiosmtpd/handlers.py | 100.00% <0.00%> (ø) |
|
aiosmtpd/controller.py | 100.00% <0.00%> (ø) |
|
aiosmtpd/proxy_protocol.py | 100.00% <0.00%> (ø) |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
All checks green, yay! The GitHub CI tests now works stably again!
Closing this because this does not need to be merged.
This is just to test GitHub CI by pushing some dummy changes.
DO NOT MERGE.