Skip to content

chore(blueprints): Add convenience build_context API that takes a StorageObject directly - #666

Merged
adam-rl merged 1 commit into
mainfrom
adam/upload_from_dir_examples
Nov 26, 2025
Merged

chore(blueprints): Add convenience build_context API that takes a StorageObject directly#666
adam-rl merged 1 commit into
mainfrom
adam/upload_from_dir_examples

Conversation

@adam-rl

@adam-rl adam-rl commented Nov 26, 2025

Copy link
Copy Markdown
Contributor

CodeAnt-AI Description

Allow build contexts to be passed as uploaded storage objects

What Changed

  • Blueprint creation now accepts a StorageObject directly for build_context and transparently turns it into the required reference.
  • Documentation now shows how to upload a local directory and hand the resulting object to the blueprint as its build context.

Impact

✅ Easier blueprint creation from local directories
✅ Clearer guidance for build-context uploads
✅ Reduced manual build-context formatting

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@adam-rl
adam-rl requested a review from dines-rl November 26, 2025 21:05
@codeant-ai

codeant-ai Bot commented Nov 26, 2025

Copy link
Copy Markdown
Contributor

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added the size:S This PR changes 10-29 lines, ignoring generated files label Nov 26, 2025
@codeant-ai

codeant-ai Bot commented Nov 26, 2025

Copy link
Copy Markdown
Contributor

Nitpicks 🔍

🔒 No security issues identified
⚡ Recommended areas for review

  • Incorrect API reference
    The new example added to describe providing a build context references sdk.objectStorage.uploadFromDir, but the SDK exposes this surface as sdk.storageObject. Customers following the example will hit a runtime error because objectStorage does not exist on RunloopSDK. Please update the example (or expose the property) so it matches the actual API surface.

Comment thread src/sdk.ts
@codeant-ai

codeant-ai Bot commented Nov 26, 2025

Copy link
Copy Markdown
Contributor

CodeAnt AI finished reviewing your PR.

@adam-rl
adam-rl force-pushed the adam/upload_from_dir_examples branch from 8f4f606 to 016fcc2 Compare November 26, 2025 21:12
@adam-rl
adam-rl force-pushed the adam/upload_from_dir_examples branch from 016fcc2 to 61a26ac Compare November 26, 2025 22:39
@github-actions

Copy link
Copy Markdown

✅ Object Smoke Tests & Coverage Report

Test Results

✅ All smoke tests passed

Coverage Results

Metric Coverage Required Status
Functions 100% 100%
Lines 86.43% - ℹ️
Branches 51.02% - ℹ️
Statements 85.97% - ℹ️

Coverage Requirement: 100% function coverage (all public methods must be called in smoke tests)

✅ All tests passed and all object methods are covered!

View detailed coverage report

Coverage reports are available in the workflow artifacts. Lines/branches/statements coverage is tracked but not required to be 100%.

📋 View workflow run

@adam-rl
adam-rl merged commit ec2beaf into main Nov 26, 2025
9 checks passed
@adam-rl
adam-rl deleted the adam/upload_from_dir_examples branch November 26, 2025 22:46
@stainless-app stainless-app Bot mentioned this pull request Nov 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S This PR changes 10-29 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants