lib.ts: adjust status logging levels

[hemberger]

GitHub reports when workflow runs log messages with notice or higher
logging levels, e.g.:

There are 0 failures, 0 warnings, and 1 notices.

Since notice was being used regardless of status, these reports were
misleading, because everything was working correctly on successes and
no-ops.

Therefore, the successes and no-ops now only log with info, and the
failures now only log with notice.

Description

Testing Instructions

Additional Notes

[codecov-commenter]

Codecov Report

Merging #1033 (358b916) into dev (76a601a) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev    #1033      +/-   ##
==========================================
- Coverage   99.59%   99.58%   -0.01%     
==========================================
  Files           7        7              
  Lines         245      243       -2     
  Branches       66       64       -2     
==========================================
- Hits          244      242       -2     
  Misses          1        1              

Impacted Files	Coverage Δ
src/lib.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 76a601a...358b916. Read the comment docs.

[JamesIves]

Is this style of reporting preferred? These were being marked as a notice so you could see at a glance the status of the action without it being marked as a warn or error.

[hemberger]

When you say "seeing it at a glance", do you mean through the workflow annotations?

If it were just that, I don't think I'd have as strong a preference. However, when this workflow runs, GitHub sends me this Discord notification:

which suggests to me that something happened that warrants my attention (albeit at a low priority level). That's how I interpret a "notice", but obviously there is some room for interpretation here.

To me at least, it is not relevant whether the workflow succeeded because there was nothing to do or because it pushed a new commit. If I'm trying to figure out why commits aren't being pushed, I'm going to be digging into the logs either way, notice or not.

Obviously it's your call here, but I would definitely prefer not to see a notice when things are working correctly.

Thanks for all your work on this great tool!

[JamesIves]

Yep and that makes sense. Appreciate the feedback and use case. I'll push this into the next release.