Skip to content
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

Catch misuses of the Var component #51081

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Jan 15, 2025

Closes #29905

Add a Vale style rule to catch docs pages in which there is a single instance of a Var. This ensures that Vars reuse information as intended.

Also fix single-instance Vars that violate the rule. For the most part, this means either:

  • Instructing the user to assign the Var, meaning that there are no easy-to-miss Vars hiding in a configuration snippet
  • Removing unnecessary Vars, e.g., if an example command is meant to illustrate a possibility and is not mean to be copied and pasted
  • Fixing mistakes in Var usage, e.g., a Proxy Service address variable that has two possible names, teleport.example.com and example.teleport.sh.

Copy link

github-actions bot commented Jan 15, 2025

Amplify deployment status

Branch Commit Job ID Status Preview Updated (UTC)
paul.gottschling/29905-var-misuses 8e60f3f 3 ✅SUCCEED paul-gottschling-29905-var-misuses 2025-01-16 18:33:20

Closes #29905

Add a Vale style rule to catch docs pages in which there is a single
instance of a Var. This ensures that Vars reuse information as intended.

Also fix single-instance Vars that violate the rule. For the most part,
this means either:

- Instructing the user to assign the Var, meaning that there are no
  easy-to-miss Vars hiding in a configuration snippet
- Removing unnecessary Vars, e.g., if an example command is meant to
  illustrate a possibility and is not mean to be copied and pasted
- Fixing mistakes in Var usage, e.g., a Proxy Service address variable
  that has two possible names, `teleport.example.com` and
  `example.teleport.sh`.
@ptgott ptgott force-pushed the paul.gottschling/29905-var-misuses branch from dc7d6c1 to 8e60f3f Compare January 16, 2025 18:27
@ptgott ptgott added this pull request to the merge queue Jan 16, 2025
auto-merge was automatically disabled January 16, 2025 18:47

Pull Request is not mergeable

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 16, 2025
@ptgott ptgott added this pull request to the merge queue Jan 16, 2025
Merged via the queue into master with commit e8b7d35 Jan 16, 2025
42 checks passed
@ptgott ptgott deleted the paul.gottschling/29905-var-misuses branch January 16, 2025 19:23
@public-teleport-github-review-bot

@ptgott See the table below for backport results.

Branch Result
branch/v15 Failed
branch/v16 Failed
branch/v17 Create PR

ptgott added a commit that referenced this pull request Jan 17, 2025
Backports #51081

Closes #29905

Add a Vale style rule to catch docs pages in which there is a single
instance of a Var. This ensures that Vars reuse information as intended.

Also fix single-instance Vars that violate the rule. For the most part,
this means either:

- Instructing the user to assign the Var, meaning that there are no
  easy-to-miss Vars hiding in a configuration snippet
- Removing unnecessary Vars, e.g., if an example command is meant to
  illustrate a possibility and is not mean to be copied and pasted
- Fixing mistakes in Var usage, e.g., a Proxy Service address variable
  that has two possible names, `teleport.example.com` and
  `example.teleport.sh`.
ptgott added a commit that referenced this pull request Jan 17, 2025
Backports #51081

Closes #29905

Add a Vale style rule to catch docs pages in which there is a single
instance of a Var. This ensures that Vars reuse information as intended.

Also fix single-instance Vars that violate the rule. For the most part,
this means either:

- Instructing the user to assign the Var, meaning that there are no
  easy-to-miss Vars hiding in a configuration snippet
- Removing unnecessary Vars, e.g., if an example command is meant to
  illustrate a possibility and is not mean to be copied and pasted
- Fixing mistakes in Var usage, e.g., a Proxy Service address variable
  that has two possible names, `teleport.example.com` and
  `example.teleport.sh`.
mvbrock pushed a commit that referenced this pull request Jan 18, 2025
Closes #29905

Add a Vale style rule to catch docs pages in which there is a single
instance of a Var. This ensures that Vars reuse information as intended.

Also fix single-instance Vars that violate the rule. For the most part,
this means either:

- Instructing the user to assign the Var, meaning that there are no
  easy-to-miss Vars hiding in a configuration snippet
- Removing unnecessary Vars, e.g., if an example command is meant to
  illustrate a possibility and is not mean to be copied and pasted
- Fixing mistakes in Var usage, e.g., a Proxy Service address variable
  that has two possible names, `teleport.example.com` and
  `example.teleport.sh`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix misuses of the Var component in the docs
3 participants