docs: clarify serviceInstanceDeployV2 default behavior and document c…#1163
Merged
Conversation
|
🚅 Deployed to the docs-pr-1163 environment in 🪄 *.railway.com
7 services not affected by this PR
|
2 tasks
MykalMachon
added a commit
that referenced
this pull request
May 18, 2026
The commitSha example introduced in #1163 used <CodeTabs> instead of <GraphQLCodeTabs>, causing the static prerender to fail with "Expected component CodeTabs to be defined" and breaking main.
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
1 participant
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.
Clarifies that
serviceInstanceDeployV2withoutcommitShadeploys the service's currently associated commit (same asserviceInstanceRedeploy), and documents thecommitShaparameter for deploying a specific commit (e.g. the latest HEAD of aconnected GitHub branch).
Prompted by customer feedback on a Slack Connect thread where the prior wording ("Trigger a new deployment" vs "Redeploy the
latest deployment") implied a behavioral difference that doesn't exist by default.