Repository navigation
Conversation
fengmk2
force-pushed
the
codex/protect-ci-secrets
branch
from
November 19, 2026 02:52
9fc8834 to
8c52356
Compare
fengmk2
force-pushed
the
codex/protect-ci-secrets
branch
from
November 20, 2026 03:15
8c52356 to
e4c99e0
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.
The GitLab trigger uses a repository secret. The bundle publisher uses an organization secret. These credentials need a policy that limits access to workflows on
main.Use separate environments for GitLab E2E and bundle publishing. Start both workflows with
workflow_dispatchonmain. GitLab E2E still checks the reviewed PR head SHA before it starts the test pipeline.Before merge, configure both environments and rotate or remove the old credentials as described in Protected Workflow Credentials.
This PR builds on #214.