Expose Kosli flow and trail as outputs from apply.yml#12
Closed
gsavage wants to merge 1 commit into
Closed
Conversation
Reusable workflows can declare outputs via on.workflow_call.outputs. Surface kosli_flow and kosli_trail so callers can do follow-up work on the same trail (e.g. extra attestations) without having to recompute the names from inputs and github context. The values are emitted from a small step in reset-drift-detection that echoes the existing KOSLI_FLOW / KOSLI_TRAIL env vars to GITHUB_OUTPUT, so the strings stay defined in a single place. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
This was added to solve a problem, but a better approach was used, and so this PR is no longer needed. |
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.
Reusable workflows can declare outputs via on.workflow_call.outputs. Surface kosli_flow and kosli_trail so callers can do follow-up work on the same trail (e.g. extra attestations) without having to recompute the names from inputs and github context.
The values are emitted from a small step in reset-drift-detection that echoes the existing KOSLI_FLOW / KOSLI_TRAIL env vars to GITHUB_OUTPUT, so the strings stay defined in a single place.