dcdpr / jp / 25954771948 / 1
65%
main: 65%

DEFAULT BRANCH: main
Ran
Files 302
Run time 6s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.726% (-0.01%) from 66.738%
25954771948.1

push

github

web-flow 
fix(attachment, github): Use fallback when diff is too large (#642)

GitHub's unified-diff endpoint (`application/vnd.github.diff`) caps
responses at 20,000 lines and returns HTTP 406 beyond that. Previously,
`jp` would surface that as an opaque error, making large PRs unusable
via the `gh:pr` attachment URI.

When the 406 is detected, the handler now falls back to the paginated
`/pulls/{N}/files` endpoint and synthesizes a unified-diff-like blob
from the per-file `DiffEntry` records. Each file gets the standard `diff
--git a/PATH b/PATH` header plus the patch hunks as returned by GitHub.
Renames and copies include the appropriate `rename from`/ `rename to`
(or `copy from`/`copy to`) markers so downstream consumers can still
identify the nature of each change.

When GitHub omits the `patch` field for a file (binary files or files
exceeding GitHub's per-file limit), a placeholder line is emitted that
surfaces the file status and line counts, ensuring the LLM still knows
the file was modified even without hunks.

The existing exclude-pattern logic applies equally to the fallback path,
so files like `Cargo.lock` or snapshot files are dropped before the
synthesized blob is assembled. A notice is injected into the PR header
whenever the fallback is used, including the count of patch-truncated
files when non-zero.

---------

Signed-off-by: Jean Mertz <git@jeanmertz.com>

26254 of 39346 relevant lines covered (66.73%)

187.72 hits per line

Source Files on job 25954771948.1