Repository navigation
Conversation
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.
Purpose
Follow-up hardening for the merged Automation v2 control plane before any repository uses
OPENAI_API_KEY.Fixes
evidence-pathand require it to resolve inside the caller checkout.gitx-access-token{ value }text formsAuthority / safety
This PR does not invoke the OpenAI API, deploy, merge, publish, spend, or modify product repositories. Keep it draft until QA and human review are complete.
Promotion gate
Only after this hardening is reviewed should a canary caller pin the reusable workflow to the immutable corrected commit SHA and exercise the newly-added organization secret.