-
Notifications
You must be signed in to change notification settings - Fork 3.9k
docs: Update variable formatting #19610
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
Conversation
|
💻 Deploy preview deleted (docs: Update variable formatting). |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-19610-to-release-3.4.x origin/release-3.4.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 34f5ae3cd875ab599e93e657ccfbfb5f7cdcb22eWhen the conflicts are resolved, stage and commit the changes: If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-19610-to-release-3.4.x
# Create the PR body template
PR_BODY=$(gh pr view 19610 --json body --template 'Backport 34f5ae3cd875ab599e93e657ccfbfb5f7cdcb22e from #19610{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'docs: Update variable formatting (backport release-3.4.x)' --body-file - --label 'size/M' --label 'type/docs' --label 'backport' --base release-3.4.x --milestone release-3.4.x --webOr, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-19610-to-release-3.4.x
# Create a pull request where the `base` branch is `release-3.4.x` and the `compare`/`head` branch is `backport-19610-to-release-3.4.x`.
# Remove the local backport branch
git switch main
git branch -D backport-19610-to-release-3.4.x |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-19610-to-release-3.5.x origin/release-3.5.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 34f5ae3cd875ab599e93e657ccfbfb5f7cdcb22eWhen the conflicts are resolved, stage and commit the changes: If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-19610-to-release-3.5.x
# Create the PR body template
PR_BODY=$(gh pr view 19610 --json body --template 'Backport 34f5ae3cd875ab599e93e657ccfbfb5f7cdcb22e from #19610{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'docs: Update variable formatting (backport release-3.5.x)' --body-file - --label 'size/M' --label 'type/docs' --label 'backport' --base release-3.5.x --milestone release-3.5.x --webOr, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-19610-to-release-3.5.x
# Create a pull request where the `base` branch is `release-3.5.x` and the `compare`/`head` branch is `backport-19610-to-release-3.5.x`.
# Remove the local backport branch
git switch main
git branch -D backport-19610-to-release-3.5.x |
(cherry picked from commit 34f5ae3)
(cherry picked from commit 34f5ae3)
What this PR does / why we need it:
Updates replacement variables to match proper formatting (upper case, underscores).