Josh Soref

Fwiw, I just released v0.0.21 a few hours ago. Yeah, I'm pretty sure this is fixed. I might have time tonight to find the version where I fixed it...

I *know* there were versions where this was a problem. [0.0.14-alpha](https://github.com/check-spelling/check-spelling/releases/tag/0.0.14-alpha) introduced a warning for [no-newline-at-eof](https://github.com/check-spelling/check-spelling/wiki/Event-descriptions#no-newline-at-eof) as well as generally fixing the problem w/ it not handling that entry. I...

This 666e47280e5c5ada3ee46c9f67d0c8ed9ac74a13 (in [v0.0.20](https://github.com/check-spelling/check-spelling/releases/tag/v0.0.20)) regressed this. -- Actually, it was worse, in that it actively ate the text whereas before it just confused the engine... I've fixed it (again) in...

It's broken in v0.0.21. It'll be fixed in v0.0.22.

https://github.com/check-spelling/check-spelling/releases/tag/v0.0.22 is now available

If that's all that's desired, then it'd be a pretty easy thing to do right here: https://github.com/actions/dependency-review-action/blob/80f10bf419f34980065523f5efca7ebed17576aa/src/comment-pr.ts#L16-L23

@cory-miller?

@jokreliable: I'd suggest you try creating a branch in your repository named `releases/test/submoduleForeach-pipelinefixes` and push to it. The workflows avoid testing on things that aren't `main` or `releases/*`, so if...

I'm running with this merged into https://github.com/check-spelling/actions-checkout/releases/tag/v3 as part of https://github.com/check-spelling/check-spelling/commit/407076ce6b63ad13212ef233a146c5a1bd479b94 in order to resolve the problem that this PR fixes in repositories such as https://github.com/check-spelling/winget-cli/actions/runs/3570503478/attempts/1 -- with this applied,...

@cory-miller, I don't have write access to this PR, but I'm hosting a rebased version of the changes here: https://github.com/actions/checkout/commit/c12e7286cb39113c32dd06ac576ed748853ee61e, you should be able to force push the branch to...