Skip to content

Fix AOR-127: Return existing commit object in 409 response for duplicate commit indexing#22

Draft
poolside-bot wants to merge 1 commit intomainfrom
fix/aor_127_bdd05c60
Draft

Fix AOR-127: Return existing commit object in 409 response for duplicate commit indexing#22
poolside-bot wants to merge 1 commit intomainfrom
fix/aor_127_bdd05c60

Conversation

@poolside-bot
Copy link
Contributor

Summary

Automated fix for AOR-127: Return existing commit object in 409 response for duplicate commit indexing

Linear Issues

Changes Made

  • action/action.yml: Added handling for 409 responses - extracts existing.id from response body and treats as success for idempotent retry behavior

…t retry

When the Bridge API returns a 409 Conflict response indicating a duplicate commit,
the action now extracts the existing commit ID from the response body and treats
the operation as successful. This enables idempotent retry behavior for GitHub
Actions workflows that are re-run after network failures.

The action checks for the 'existing.id' field in the 409 response. If found, it
logs the existing commit ID and exits successfully. If not found (backward
compatibility with older backend versions), it falls through to the standard
error handling.

Closes: AOR-127
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