Rework the logging to distinguish "skipping updates" from "already updated" #695
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
logging
Related to what the tool outputs to the end user
Milestone
The current logging is confusing because it does not distinguish cached API results from genuine ones. It means the user might think the tool is performing real checking and updating while it's just using cached results. Inspired by the discussions in #680.
This enhancement requires slight adjustments to the internal API to expose whether the result is cached or not.
Maybe some documentation changes, too.
The text was updated successfully, but these errors were encountered: