Skip to content

Retry git-data writes GitHub hasn't replicated yet; README badges - #4

Merged
wandermyz merged 2 commits into
mainfrom
fix-git-data-lag
Oct 18, 2026
Merged

wandermyz merged 2 commits into
mainfrom
fix-git-data-lag

Conversation

@wandermyz

Copy link
Copy Markdown
Owner
  • Fixes the CI flake on main where createCommit failed with 422 "Tree SHA does not exist" right after createTree. createTree, createCommit and updateRef now retry that kind of 422 (0.5s, 1s, 2s). The same code backs the plugin's push, so users benefit too. A non-fast-forward 422 still fails at once, so race detection is unchanged; there's a unit test for it.
  • README: CI and latest-release badges.

🤖 Generated with Claude Code

wandermyz and others added 2 commits October 18, 2026 02:21
createCommit right after createTree has failed with 422 "Tree SHA does not
exist" (seen in CI): GitHub's git database is replicated and a fresh object
can briefly be invisible. createTree, createCommit and updateRef now retry
that kind of 422 after a short wait (0.5s, 1s, 2s). Other 422s, including a
ref update that isn't a fast-forward, still fail at once, so the push's race
detection is unchanged. This applies to the plugin's push as well as the
test scaffolding, which goes through the same client.

README: CI and latest-release badges.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The engine e2e and the in-Obsidian suites run concurrently in CI against the
same branch. A test's push could see the branch moved by the other suite and
correctly report "raced" before reaching what it meant to test, e.g. the
mass-deletion guard. Push through a helper that pulls and retries on a race,
like the plugin's sync loop; the deliberate stale-push test still pushes
directly.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@wandermyz
wandermyz merged commit 04063b3 into main Oct 18, 2026
6 checks passed
@wandermyz
wandermyz deleted the fix-git-data-lag branch October 18, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant