-
Notifications
You must be signed in to change notification settings - Fork 11.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: update Sui environment setup #18303
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
@emmanuel-ferdman is attempting to deploy a commit to the Mysten Labs Team on Vercel. A member of the Team first needs to authorize it. |
This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Thanks @emmanuel-ferdman ! |
Hi @ronny-mysten @aschran @Jordan-Mysten @williampsmith @amnn, can you please review this small PR when you get the chance? |
Looks like because the PR is so old, we'll need to rebase it and re-submit so CI can run. @emmanuel-ferdman, could you do that? Then I'll be able to make sure it gets landed. |
Signed-off-by: Emmanuel Ferdman <[email protected]>
8b29a72
to
28aa254
Compare
@amnn should be good now - the branch is updated to latest changes in |
Description
PR #17253 moved the location of the Sui environment setup file. This PR adjusts sources to changes.
Test plan
Checked the doc.
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.