Barry Pollard

That is true and certainly a risk. In my case they are built into HTML and and we do lint those. But apparently the HTML linter we use (HTMLHint) is...

There can be a lot. Here’s an example one if you’re curious: https://github.com/HTTPArchive/almanac.httparchive.org/blob/main/src/content/en/2021/css.md We also have translations and one thing that’s particularly apparent with this new link is the translators...

So there are anything for a few to many figure links. That particular document has 67 figures. You can see [the final published version here](https://almanac.httparchive.org/en/2021/css). In this example none of...

FYI I managed to work around this using [inline ignores](https://github.com/DavidAnson/markdownlint#configuration) on the affected lines since, luckily, we don't reference figures that much internally so this is feasible. I still think...

Fair points. I think changing to pass instead of notApplicable as you suggest is the best we can get then.

@benschwarz this could be an alternative way to handle forks, if people didn't want to merge uncompressed images followed by a PR to compress them like I added in #54...

Actually, thinking about this some more, you could do this already with the following workflow: ```yml name: Check Images are Compressed on: pull_request: # Run image-actions when jpg, jpeg, png...

Thanks @benschwarz ! Please find attached all the details [CalibreVsTinyPNG-Details.xlsx](https://github.com/calibreapp/image-actions/files/5716333/CalibreVsTinyPNG-Details.xlsx) It looks to me like the histogram is about half the size - which is directly reflected in the file...

Agree this would be useful. And agree currently it does all files each time - that's working as intended at the moment btw, rather than a bug per se, though...

Think when you get into cropping you're asking for trouble. One thing I'd like is just to ensure no one uploads a print quality 6000 x 3000 image when a...