Skip to content

[Chore] Add noindex to Wrangler 1 pages #22758

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 29, 2025
Merged

[Chore] Add noindex to Wrangler 1 pages #22758

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...ent/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/authentication.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ pcx_content_type: how-to
title: Authentication
sidebar:
order: 2
noindex: true
---

import { Render } from "~/components";
Expand Down
3 changes: 1 addition & 2 deletions src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ sidebar:
head:
- tag: title
content: Commands - Wrangler v1 (deprecated)
noindex: true
---

import { Render, Type, MetaInfo, WranglerConfig } from "~/components";
Expand Down Expand Up @@ -540,8 +541,6 @@ Most `kv` commands require you to specify a namespace. A namespace can be specif

Most `kv` subcommands also allow you to specify an environment with the optional `--env` flag. This allows you to publish Workers running the same code but with different namespaces. For example, you could use separate staging and production namespaces for KV data in your Wrangler file:



<WranglerConfig>

```toml
Expand Down
Loading
Loading