chore(ci): setup automated stainless builds #3557
Open
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
dgellow
requested review from
ashwinb,
yanxi0830,
hardikjshah,
raghotham,
ehhuang,
terrytangyuan,
leseb,
bbrowning,
reluctantfuturist,
mattf and
slekkala1
as code owners
meta-cla
bot
added
the
CLA Signed
slekkala1
reviewed
Sep 29, 2025
|
|
||
| # Path to your Stainless config. Optional; only provide this if you prefer | ||
| # to maintain the ground truth Stainless config in your own repo. | ||
| CONFIG_PATH: ./docs/static/stainless-config.yaml |
There was a problem hiding this comment.
what would other option be? is this maintained in the stainless-sdk repo?
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.
What does this PR do?
This pull request adds a new workflow that does 2 things:
Important
A llama-stack admin will need to add a new secret
STAINLESS_API_KEY. The API key can be created in the Stainless org dashboard.Test Plan
I tested in my fork: stainless-api#3