ci: split run_examples to keep PR runs unsecured and gate API runs to main#531
Merged
Merged
Conversation
… main - run_examples: build + install only, no secrets, no env, runs on PR + push - examples: build + run examples with CI_MISTRAL_API_KEY_PYTHON_*, environment: publish, push-to-main only Pins runners to ubuntu-24.04 while here.
Nelson-PROIA
force-pushed
the
chore/split-run-examples-for-env-gating
branch
from
b610cec to
5a91586
Compare
louis-sanna-dev
approved these changes
May 19, 2026
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
2 participants
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.
Summary
Split the examples workflow so that secret-using jobs only run on push to
mainbehind an environment gate.run_examples(build + install, no secrets, no environment, runs on PR + push to main)examples(build + run examples withCI_MISTRAL_API_KEY_PYTHON_*,environment: publish, push-to-main only)ubuntu-24.04Why
Today's workflow runs the API-key job on every PR with no environment gating. This change keeps PRs unblocked (build-only) and routes the API-key step through the
publishenvironment so it requires reviewer approval before running.Verification
publishenvironment already has all fourCI_MISTRAL_API_KEY_PYTHON_{310,311,312,313}secrets