workflow: add hook conflict inspection - #328
Draft
fantix wants to merge 1 commit into
Draft
Conversation
fantix
force-pushed
the
fantix/hook-get-conflict
branch
from
August 25, 2026 20:14
88d3e27 to
a5b4ca3
Compare
fantix
force-pushed
the
fantix/hook-get-conflict
branch
from
August 26, 2026 18:40
a5b4ca3 to
eee3310
Compare
fantix
force-pushed
the
fantix/hook-get-conflict
branch
from
August 27, 2026 01:44
eee3310 to
349a832
Compare
fantix
force-pushed
the
fantix/hook-get-conflict
branch
from
August 27, 2026 18:48
349a832 to
a6b0d8f
Compare
* Preserve the owner run ID on hook conflict events. * Add get_conflict() to check token ownership without consuming payload. * Materialize lazy Vercel hook conflict events so the runtime can inspect them.
fantix
force-pushed
the
fantix/hook-get-conflict
branch
from
August 27, 2026 18:57
a6b0d8f to
94e2aad
Compare
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
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.
This PR adds support for a workflow to check whether a hook token is already in use without waiting for someone to send data to the hook.
New public API:
HookEvent.get_conflict() -> Run[Any] | None. Calling it claims the token for this hook if the token is free. It returnsNonein that case, or the owningRunif another hook already uses the token.HookEvent.get_conflict()to claim a token without waiting for hook data.Runfrom repeated conflict checks.