Skip to content

DOC-5419 added commands section #1797

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

Merged
merged 2 commits into from
Jul 3, 2025
Merged

Conversation

andy-stark-redis
Copy link
Contributor

@andy-stark-redis andy-stark-redis commented Jul 2, 2025

DOC-5419

Building on the previous restructure, a suggestion for a different place to put the transactions and pipelining pages, along with the keyspace page and a general intro.

Copy link
Contributor

github-actions bot commented Jul 2, 2025

Staging links:
https://redis.io/docs/staging/DOC-5419-commands-section/commands/command
https://redis.io/docs/staging/DOC-5419-commands-section/commands/scan
https://redis.io/docs/staging/DOC-5419-commands-section/develop/ai/search-and-query/best-practices/index-mgmt-best-practices
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/dotnet/condexec
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/dotnet/transpipe
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/go/transpipe
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/hiredis/transpipe
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/jedis/transpipe
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/nodejs/transpipe
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/pools-and-muxing
https://redis.io/docs/staging/DOC-5419-commands-section/develop/clients/redis-py/transpipe
https://redis.io/docs/staging/DOC-5419-commands-section/develop/data-types/hashes
https://redis.io/docs/staging/DOC-5419-commands-section/develop/get-started/data-store
https://redis.io/docs/staging/DOC-5419-commands-section/develop/get-started/vector-database
https://redis.io/docs/staging/DOC-5419-commands-section/develop/programmability/
https://redis.io/docs/staging/DOC-5419-commands-section/develop/programmability/eval-intro
https://redis.io/docs/staging/DOC-5419-commands-section/develop/programmability/functions-intro
https://redis.io/docs/staging/DOC-5419-commands-section/develop/reference/protocol-spec
https://redis.io/docs/staging/DOC-5419-commands-section/develop/using-commands/
https://redis.io/docs/staging/DOC-5419-commands-section/develop/using-commands/keyspace
https://redis.io/docs/staging/DOC-5419-commands-section/develop/using-commands/pipelining
https://redis.io/docs/staging/DOC-5419-commands-section/develop/using-commands/transactions
https://redis.io/docs/staging/DOC-5419-commands-section/operate/rc/databases/configuration/sizing

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a dodgy link in the following paragraph toward the bottom of the page. It's probably been there for a while.

**Warning**: consider [`KEYS`]({{< relref "/commands/keys" >}}) as a command that should only be used in production
environments with extreme care.

[`KEYS`]({{< relref "/commands/keys" >}}) may ruin performance when it is executed against large databases.
This command is intended for debugging and special operations, such as changing
your keyspace layout.
Don't use [`KEYS`]({{< relref "/commands/keys" >}}) in your regular application code.
If you're looking for a way to find keys in a subset of your keyspace, consider
using [`SCAN`]({{< relref "/commands/scan" >}}) or [sets][{{< relref "/develop/data-types/sets" >}}].

The last link has square brackets around the relref, which should be changed to round brackets.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dwdougherty Well spotted! I've fixed it now.

Copy link
Collaborator

@dwdougherty dwdougherty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this re-org. So, apart from the one dodgy link mentioned above, LGTM.

@andy-stark-redis
Copy link
Contributor Author

Thanks @dwdougherty !

Copy link
Collaborator

@mich-elle-luna mich-elle-luna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you!

@andy-stark-redis
Copy link
Contributor Author

Thanks @mich-elle-luna !

@andy-stark-redis andy-stark-redis merged commit ac3291f into main Jul 3, 2025
4 checks passed
@andy-stark-redis andy-stark-redis deleted the DOC-5419-commands-section branch July 3, 2025 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants