Trigger workflows from a tag push - #14
Merged
Merged
Conversation
Pushing ios-build/<id> or ios-share/<id> starts the same job as the workflow_dispatch, for environments where the GitHub API is not reachable. A push event runs the workflow file from the tagged commit and has no inputs, so a "Resolve parameters" step reads the settings from builder.json there, with the dispatch defaults, and every later step reads its outputs. The job deletes the tag when it ends.
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
1 participant
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.
Pushing a tag
ios-build/<id>orios-share/<id>now starts the build or simulator workflow without the GitHub API, for environments where only git access is available.inputs, so a new Resolve parameters step readsios.path,ios.scheme,ios.signing,ios.configuration,flutter.versionandkmp.jdkVersionfrombuilder.jsonin the tagged commit, falling back to the dispatch defaults. Dispatch runs pass their inputs through unchanged. All later steps read that step's outputs instead ofinputs.*.contents: writeon the job token.Verified: YAML parses, the parameter script was exercised locally against a sample
builder.jsonon a simulated push event,go test ./...passes. Not exercised against a live GitHub tag push.Note: a push-triggered run uses the workflow file from the tagged commit, and any other workflow with an unfiltered
on: pushfires on these tags too.🤖 Generated with Claude Code
https://claude.ai/code/session_01JfXAVZQvVmRFFNdYLc39Tv