Hyperlint Automation: Meta Description Fixes #20443
Closed
Conversation
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
Contributor
|
Howdy and thanks for contributing to our repo. We review new, external PRs within 2 weeks. If it's been longer than then without any movement, tag the PR Assignees in a comment. |
Contributor
|
CI run failed: build logs |
pedrosousa
reviewed
Mar 6, 2025
|
|
||
| <Render file="rules-creation-dash-dns-popup" /> | ||
|
|
||
| ---\ntitle: Create a rule in the dashboard\npcx_content_type: how-to\ndescription: Learn how to create URL rewrite rules in the Cloudflare dashboard using wildcard patterns. Configure dynamic paths and queries for efficient URL management.\nsidebar:\n order: 2\nhead:\n - tag: title\n content: Create a rewrite URL rule in the dashboard\n---\n\nimport { Render } from "~/components";\n\nRefer to the [Rules examples gallery](/rules/transform/examples/?operation=Rewrite+URL) for examples of rule definitions.\n\nTo create a rule:\n\n1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and website.\n\n2. Go to **Rules** > **Overview**.\n\n3. Select **Create rule** > **URL Rewrite Rule**.\n\n4. (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration.\n\n5. Enter a descriptive name for the rule in **Rule name**.\n\n \n\n6. Under **If incoming requests match**, select one of the following options:\n\n - **Wildcard pattern**: The rule will only apply to traffic matching the wildcard pattern in **Request URL**. Refer to [Wildcard pattern parameters](#wildcard-pattern-parameters) for details.\n\n - **Custom filter expression**: The rule will only apply to traffic matching a custom expression. Define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/) to configure which requests should be rewritten. Use either the Expression Builder or the Expression Editor to define the custom expression. For more information, refer to [Edit expressions in the dashboard](/ruleset-engine/rules-language/expressions/edit-expressions/).\n\n :::note\n Check the [fields and functions](/rules/transform/url-rewrite/reference/fields-functions/) you can use in filter expressions of rewrite URL rules.\n :::\n\n - **All incoming requests**: The rule will apply to all traffic.\n\n7. (Optional) Define the action for your rewrite URL rule by selecting one of the available options displayed as radio buttons, and then a value from the drop-down list, depending on the action:\n\n - If you select **Rewrite to** > _Static_, enter the string that will replace the original URL path (or query string). For example, enter `welcome-gb.html` to rewrite the original URL path to `/welcome-gb.html`.\n\n - If you select **Rewrite to** > _Dynamic_, enter a [rewrite expression](/rules/transform/url-rewrite/reference/fields-functions/#rewrite-expressions) that defines the dynamic URL rewrite to perform.\n\n - If you do not want to change the value of a component of the original request (the URL path or the URL query string), choose _Preserve_ for that component.\n\n For more information, refer to [URL rewrite parameters](/rules/transform/url-rewrite/reference/parameters/).\n\n8. (Optional) Under **Place at**, define where to place the rule in the rules list: first rule in the list, last rule in the list, or in a custom position (after a given rule).\n\n9. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.\n\n <Render file="rules-creation-dash-dns-popup" /> |
Contributor
There was a problem hiding this comment.
@bllchmbrs Same issue here as seen before, with "\n" characters in the proposed changes instead of real line breaks.
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.
Meta Description Fix Proposal(s)
The goal of this pull request is to improve the meta description for pages in the documentation.
Proposing changes to the following files:
to edit this branch locally, run:
🗣️Leave us feedback
This pull request is part of a series of Hyperlint Automations to ease the burden of maintaining documentation.
We'll be introducing this automation, and others, over the coming months. These automations will always open pull requests(or issues) prior to making changes.
If this is not the change you want, please close this pull request and let us know what you'd like to see.
This feature may introduce erroneous changes (although we work hard to make sure that doesn't happen). Please review the changes before merging.
❌ Limitations:
At this time, Hyperlint can't respond to pull requests or issues.
📩 Need Help?
Please reach out to support with any requests, questions, or concerns.