Notify users about duplicate jobs#780
Merged
Merged
Conversation
f-f
force-pushed
the
notify-duplicate-jobs
branch
from
July 22, 2026 09:21
5045537 to
09a40f2
Compare
Amp-Thread-ID: https://ampcode.com/threads/T-019f86f1-9f56-74be-9212-ad76f3ce6492 Co-authored-by: Thomas Honeyman <admin@thomashoneyman.com> Amp-Thread-ID: https://ampcode.com/threads/T-019f86f1-9f56-74be-9212-ad76f3ce6492
f-f
force-pushed
the
notify-duplicate-jobs
branch
from
July 22, 2026 09:38
09a40f2 to
0159443
Compare
f-f
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #748. We now notify GitHub issue submitters when their operation matches an existing job instead of polling that job and replaying its previous logs or failure.
API behavior
Job submission endpoints now distinguish new and duplicate submissions using the HTTP status:
201 Createdwhen a new job is inserted200 OKwhen an existing duplicate job is returnedBoth responses retain the existing V1 JSON body:
{ "jobId": "..." }This keeps the V1 wire format compatible while allowing clients to distinguish the two outcomes using standard HTTP semantics. The behavior applies consistently to publish, unpublish, transfer, and package-set submissions.
GitHub issue behavior
When the GitHub issue client receives a duplicate response, it:
New jobs continue through the existing polling and reporting workflow.