pub const CONFLICT_WORDINGS: [&str; 1];Expand description
The wordings GitHub answers a write that collided with another change to the same
ordering with, in the errors of an HTTP 200: “Your attempt to move this item created a
temporary conflict. Please try again.” The write did not take effect and GitHub asks for it
again, so it is retried on the same growing schedule a rate limit without a hint is, within
the same retry budget — except a createIssue, whose answer cannot say the issue was not
made, and which is therefore reported rather than replayed into a duplicate.
Observed rather than documented, so it is pinned exactly as SECONDARY_WORDINGS is:
tests/fixtures/rate-limits.json records where it was read under conflict.observed, and
the same drift gate reconciles the two both ways. Public for that gate alone.