You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a Hub workflow to act on pull requests when they are opened. After review feedback, contributors can push more commits or otherwise change the head of the same pull request. I want Hub to run a follow-up workflow against the new head so the automation works with the current code.
Current limitation
Hub has semantic GitHub triggers for pull request creation, comments, and labels, but not for changes to an existing pull request head. github.pull_request_created covers only the initial opening, so later head updates cannot be expressed through the semantic trigger set.
Desired flow
A pull request is opened and the initial workflow runs.
A contributor updates the pull request head.
GitHub sends a pull_request event with the synchronize action.
Hub starts the configured follow-up workflow with the updated pull request context.
Existing repository, sender, and other GitHub filters apply normally.
Possible direction
Add a semantic event such as github.pull_request_updated, classified only from pull_request.synchronize. Metadata-only actions such as edited would not match it, and existing raw and semantic GitHub triggers would keep their current behavior.
The public name is intentionally open for discussion: pull_request_updated is approachable, while a name such as pull_request_head_updated would describe the boundary more precisely.
I have a focused Hub implementation and automated coverage ready. I can open the Hub implementation PR and companion public-docs PR once the event semantics and name are agreed.
Would this workflow fit Hub, and which semantic event name would be preferred?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Workflow
I use a Hub workflow to act on pull requests when they are opened. After review feedback, contributors can push more commits or otherwise change the head of the same pull request. I want Hub to run a follow-up workflow against the new head so the automation works with the current code.
Current limitation
Hub has semantic GitHub triggers for pull request creation, comments, and labels, but not for changes to an existing pull request head.
github.pull_request_createdcovers only the initial opening, so later head updates cannot be expressed through the semantic trigger set.Desired flow
pull_requestevent with thesynchronizeaction.Possible direction
Add a semantic event such as
github.pull_request_updated, classified only frompull_request.synchronize. Metadata-only actions such aseditedwould not match it, and existing raw and semantic GitHub triggers would keep their current behavior.The public name is intentionally open for discussion:
pull_request_updatedis approachable, while a name such aspull_request_head_updatedwould describe the boundary more precisely.I have a focused Hub implementation and automated coverage ready. I can open the Hub implementation PR and companion public-docs PR once the event semantics and name are agreed.
Would this workflow fit Hub, and which semantic event name would be preferred?
All reactions