chore: fix paths to sandboxed code execution examples #2381
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
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
jog1t
force-pushed
the
04-24-chore_fix_paths_to_sandboxed_code_execution_examples
branch
from
b0e6205 to
25a00d4
Compare
Deploying rivet-studio with
|
| Latest commit: |
34393da
|
| Status: | ⚡️ Build in progress... |
Deploying rivet-hub with
|
| Latest commit: |
25a00d4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://51440ce3.rivet-hub-7jb.pages.dev |
| Branch Preview URL: | https://04-24-chore-fix-paths-to-san.rivet-hub-7jb.pages.dev |
Deploying rivet with
|
| Latest commit: |
25a00d4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://39fa5b1f.rivet.pages.dev |
| Branch Preview URL: | https://04-24-chore-fix-paths-to-san.rivet.pages.dev |
NathanFlurry
force-pushed
the
04-24-chore_fix_paths_to_sandboxed_code_execution_examples
branch
from
25a00d4 to
b0e6205
Compare
jog1t
force-pushed
the
04-24-chore_fix_paths_to_sandboxed_code_execution_examples
branch
from
b0e6205 to
25a00d4
Compare
NathanFlurry
force-pushed
the
04-24-chore_fix_paths_to_sandboxed_code_execution_examples
branch
from
25a00d4 to
b0e6205
Compare
NathanFlurry
force-pushed
the
04-24-chore_fix_paths_to_sandboxed_code_execution_examples
branch
from
b0e6205 to
34393da
Compare
Merge activity
|
graphite-app bot
pushed a commit
that referenced
this pull request
Apr 25, 2025
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->
graphite-app
bot
deleted the
04-24-chore_fix_paths_to_sandboxed_code_execution_examples
branch
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Summary
This PR reorganizes the sandboxed code execution examples by renaming directories and updating paths to better reflect their purposes, with 'eval' for code evaluation and 'standalone' for independent execution.
- Renamed
sandboxed-code-execution-jstosandboxed-code-execution-evalto clarify its code evaluation focus - Renamed
sandboxed-code-execution-dockertosandboxed-code-execution-standalonefor standalone execution examples - Fixed inconsistency in
upload_js.tswhereprocess.envis used instead ofDeno.env - Removed unused
uuidv4import inupload_js.tswhilecrypto.randomUUIDis being used - Fixed duplicate
PROJECTconstant declaration inupload_js.ts
10 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
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.
Changes