Josh Soref

@tsinis interesting. Fwiw, I'm surveying the landscape because I've been asked about doing something for a project, and I'm currently trying to understand why I shouldn't just use `gh pr...

It should also explain how this API differs from the `/code-scanning/sarifs` endpoint.

For people curious about this endpoint, it uses `PUT` instead of `POST`. As with [`/repos/:owner/:repo/code-scanning/sarifs`](https://docs.github.com/en/rest/code-scanning/code-scanning?apiVersion=2022-11-28#upload-an-analysis-as-sarif-data), when it's happy, it returns a [`202`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/202). Unlike the `/code-scanning/sarifs` endpoint, it does not return...

Hmm... It's definitely possible to implement this. I have most of the code already in the form of the code to collapse comments. These days, I generally disable the comment...

Note that for the past couple of releases, check-spelling has collapsed comments which at least means that most readers don't have to read the old comments. (I'm aware it isn't...

Tentatively, my suggestion is to use: [`post_comment`](https://docs.check-spelling.dev/Configuration.html#postcomment) So: ```yaml with: post_comment: 0 ``` To avoid this problem and rely on the step summary. Note that if you switch to using...

Here's a reduced version based on the files: [nytprof-227.t](https://github.com/user-attachments/files/19653952/nytprof-227.txt) ```sh root@lima-rancher-desktop:/tmp# ./nytprof-227.t 1..1 Use of uninitialized value $Broken::sometimes_undefined in regexp compilation at ./nytprof-227.t line 21. Use of uninitialized value $Broken::sometimes_undefined...

Another case: https://github.com/check-spelling-sandbox/internet-draft-template/actions/runs/14171037329/job/39694680330 The log says: ```sh git fetch -qf origin gh-pages:gh-pages fatal: couldn't find remote ref gh-pages make: [lib/ghpages.mk:60: fetch-ghpages] Error 128 (ignored) Error: No gh-pages branch, run `make...

That's fine. I figured `make` was doing the hard work. I'm not in a hurry. For reference, for my own (composite) action, I have an extra step that runs in...

Personally, I'd be inclined to put it next to update available. But if you put it there, the button shouldn't be labeled "Retry", just "Check for updates" But, arguably any...