GeezerVison is showing github.com — chore: blame-ignore the #150 squash; retry the bun download in the npm image by mikolalysenko · Pull Request #156 · SocketDev/socket-patch
Conversation
Summary
Two pieces of post-merge housekeeping from #150:
-
.git-blame-ignore-revs (new file) listing the Structure-review batch: sweep fixes, module taxonomy, npm-family dedup, coverage gaps, CI honesty #150 squash commit (08ea9ba): it contains the pure-rename taxonomy moves (patch/vendor → vendor/, the setup/ umbrella, the utils dissolve) plus ~50 files of mechanical import repoints. The Structure-review batch: sweep fixes, module taxonomy, npm-family dedup, coverage gaps, CI honesty #150 PR body deferred this until the squash SHA existed. Enable locally with git config blame.ignoreRevsFile .git-blame-ignore-revs; GitHub's blame view picks the file up automatically.
-
Dockerfile.npm bun install retry: the first post-merge main run lost coverage-docker (npm) to a transient GitHub-releases CDN drop inside curl -fsSL https://bun.sh/install | bash (curl: (56) Connection died, tried 5 times) — the install script has no retry of its own. Three attempts with 10s/20s backoff. (That failed job has been rerun independently; this prevents the next occurrence.)
🤖 Generated with Claude Code
Note
Low Risk
Developer tooling and CI image build resilience only; no runtime product or security-sensitive logic changes.
Overview
Adds .git-blame-ignore-revs so git blame (and GitHub blame) can skip the #150 squash commit (08ea9ba)—taxonomy renames and mechanical import updates across many files—instead of attributing that churn to the merge. Local setup is documented via git config blame.ignoreRevsFile .git-blame-ignore-revs.
In tests/docker/Dockerfile.npm, the bun install step is wrapped in three attempts with 10s/20s backoff before failing the image build, because the official install script’s single curl to GitHub releases has no retry and transient CDN failures have broken CI.
Reviewed by Cursor Bugbot for commit c05cdb7. Configure here.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
…m image
* .git-blame-ignore-revs (new): the #150 squash merge contains the
pure-rename taxonomy moves plus ~50 files of mechanical import
repoints — exactly the churn blame should skip. The PR body deferred
this to post-merge since the squash SHA only exists now.
* Dockerfile.npm: bun's install script downloads the release zip from
GitHub with no retry, and a single transient CDN drop ("curl: (56)
Connection died") failed the whole coverage-docker (npm) image build
on the first post-merge main run. Three attempts with backoff.
Co-Authored-By: Claude Fable 5 <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.