Skip to content

0.139.1: push goes on past keeper_only and the other element 403s - #26

Merged
tmoosting merged 1 commit into
mainfrom
push-keeper-only
Nov 21, 2026
Merged

tmoosting merged 1 commit into
mainfrom
push-keeper-only

Conversation

@tmoosting

Copy link
Copy Markdown
Member

push stopped the whole run on any 403 but not_author. keeper_only (a world's Charter and the elements it names change only by the owner and co-builders), review_by_another and not_reader are each about one element, so that patch now fails and the run goes on; any other 403, and an unknown code, still stops it. Both directions watched failing.

🤖 Generated with Claude Code

A world's Charter and the elements it names now change only by the owner and
co-builders (403 keeper_only). push treated every 403 but not_author as a
refusal of the key and stopped the run, so a contributor's push that met one
such element left its other edits unsent. keeper_only, review_by_another and
not_reader are about one element too: that patch fails and the run goes on.
Any other 403, and an unknown code, still stops it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tmoosting
tmoosting merged commit 43c5457 into main Nov 21, 2026
11 checks passed

This branch was successfully deployed

1 active deployment
pypi — 43c5457e Deployed Nov 21, 2026 by tmoosting via publish #224
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