Codecov Report

Merging #21 (63d2211) into main (f53976a) will increase coverage by 0.82%.
The diff coverage is 90.47%.

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
+ Coverage   80.68%   81.51%   +0.82%     
==========================================
  Files           6        6              
  Lines         647      649       +2     
==========================================
+ Hits          522      529       +7     
+ Misses        125      120       -5     

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

The solution for this is going to need more than just a few lines changed. I'll start hacking it...

This branch is now overwritten by my changes to properly address #18.

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

The unit tests agree with you. If released, this would be a patch version bump. I'm ready when you are.

I'm ready, let me test it in action after release.

FYI, I added your p_enemy.c file to the unit test for precision.

So I need to keep p_enemy.c file always in the test-repo? at least I need to keep test-repo always existing, I think I will not delete it.

I'm going to merge this pull request.

So I need to keep p_enemy.c file always in the test-repo? at least I need to keep test-repo always existing, I think I will not delete it.

You shouldn't need to since the file's "added" state is specific to the commit that was pushed to the remote. I don't think GitHub deletes orphaned branches/commits.

We could always change the file to a new file in this repo's demo src. Ironically, the name p_enemy.c is also used in chocolate-doom (which we also use in the unit test), but there's no conflict because chocolate-doom's file is located in src/hexen/p_enemy.c (your file is in the supposed repo-root).