Skip to content

Conversation

@JStickler
Copy link
Contributor

What this PR does / why we need it:

Updates replacement variables to match proper formatting (upper case, underscores).

@JStickler JStickler requested a review from a team as a code owner October 27, 2025 21:26
@JStickler JStickler added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Oct 27, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 27, 2025

💻 Deploy preview deleted (docs: Update variable formatting).

@JStickler JStickler merged commit 34f5ae3 into main Oct 28, 2025
71 checks passed
@JStickler JStickler deleted the ReplacementVariables branch October 28, 2025 20:24
@loki-gh-app
Copy link
Contributor

loki-gh-app bot commented Oct 28, 2025

The backport to release-3.4.x failed:

The process '/usr/bin/git' failed with exit code 1

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 34f5ae3cd875ab599e93e657ccfbfb5f7cdcb22e

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

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 --web

Or, 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

@loki-gh-app
Copy link
Contributor

loki-gh-app bot commented Oct 28, 2025

The backport to release-3.5.x failed:

The process '/usr/bin/git' failed with exit code 1

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 34f5ae3cd875ab599e93e657ccfbfb5f7cdcb22e

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

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 --web

Or, 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

JStickler added a commit that referenced this pull request Oct 28, 2025
JStickler added a commit that referenced this pull request Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport release-3.4.x backport release-3.5.x backport-failed size/M type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants