Skip to content

Add Feature Flags docs #2585

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Add Feature Flags docs #2585

wants to merge 4 commits into from

Conversation

Resonance1584
Copy link
Contributor

@Resonance1584 Resonance1584 commented May 12, 2025

Summary by CodeRabbit

  • New Features

    • Added documentation for Pipelines feature flags, detailing available flags, descriptions, defaults, and usage instructions.
    • Introduced a new "Ignore List" feature, with documentation explaining how to configure file ignore patterns in pipeline configurations (HCL and YAML).
    • Updated sidebar navigation to include "Ignore List" and "Feature Flags" documentation entries.
    • Documented new configuration options for specifying ignore filters in both YAML and HCL pipeline configurations.
  • Documentation

    • Expanded documentation to cover new pipeline configuration options and detailed usage examples for ignore patterns.
    • Added new terms to the custom dictionary for improved documentation consistency.

Copy link

vercel bot commented May 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 16, 2025 9:30pm

Copy link
Contributor

coderabbitai bot commented May 12, 2025

Walkthrough

This update introduces new documentation for Pipelines feature flags and the ignore list functionality, adds corresponding sidebar entries, and updates configuration documentation to describe how to use ignore filters in both HCL and YAML formats. Additionally, two new terms were added to the custom dictionary.

Changes

File(s) Change Summary
docs/2.0/reference/pipelines/feature-flags.md Added new documentation describing available Pipelines feature flags, their usage, defaults, and configuration details.
docs/2.0/reference/pipelines/ignore-list.md Added new documentation explaining the Pipelines Ignore List feature, syntax, and common usage patterns.
sidebars/reference.js Added sidebar entries for "Ignore List" and "Feature Flags" under Gruntwork Pipelines.
docs/2.0/reference/pipelines/configurations-as-code/api.md Documented new optional ignore_list attribute for the repository block, with a reference to ignore list docs.
docs/2.0/reference/pipelines/configurations.md Documented new required ignore-list configuration option under pipelines in YAML configuration docs.
custom-dictionary.txt Added "myvars" and "myfile" to the custom dictionary.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Docs
    participant Pipelines

    User->>Docs: Reads about feature flags and ignore list
    User->>Pipelines: Configures feature flags via env vars in HCL/YAML
    User->>Pipelines: Sets ignore-list patterns in config
    Pipelines->>Pipelines: Applies feature flags and ignore filters during run
Loading

Possibly related PRs

  • Add Stacks documentation #2525: Adds a detailed guide on using Terragrunt Stacks, which is referenced in the new Pipelines feature flags documentation for enabling stack support.

Poem

New docs arrive with patterns to ignore,
Feature flags unlocked—experiments galore!
YAML and HCL, now clearer than before,
"myvars" and "myfile" join the lexicon’s core.
Pipelines march onward, with configs in tow,
Knowledge blooms—let your productivity grow!

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (2)
docs/2.0/reference/pipelines/feature-flags.md (2)

8-13: Grammar: add commas for clarity

  • After “e.g.” add a comma: “e.g., when both FileChanged…”
  • After “Additionally” add a comma: “Additionally, pipelines will execute…”
🧰 Tools
🪛 LanguageTool

[uncategorized] ~12-~12: A comma may be missing after the conjunctive/linking adverb ‘Additionally’.
Context: ...hould trigger a plan in the same unit. Additionally pipelines will execute terragrunt with ...

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

🪛 markdownlint-cli2 (0.17.2)

8-8: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


47-75: Consistent headings & reduce repetition

  • Update the remaining flag headings from #### to ### to maintain a proper heading hierarchy.
  • The sentence “This is a break-glass feature flag and can be used to disable this functionality if it is causing issues.” appears twice; consider extracting it into a shared note or rephrasing one occurrence for variety.
🧰 Tools
🪛 LanguageTool

[style] ~66-~66: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ands like terragrunt stack generate. This is a break-glass feature flag and can b...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fac88a2 and 0f288b3.

📒 Files selected for processing (2)
  • docs/2.0/reference/pipelines/feature-flags.md (1 hunks)
  • sidebars/reference.js (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/2.0/reference/pipelines/feature-flags.md

[uncategorized] ~12-~12: A comma may be missing after the conjunctive/linking adverb ‘Additionally’.
Context: ...hould trigger a plan in the same unit. Additionally pipelines will execute terragrunt with ...

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)


[typographical] ~35-~35: It seems that a comma is missing.
Context: ...dir1/myvars.json ``` When this flag is enabled Pipelines will detect changes to `dir1/...

(IF_COMMA)


[duplication] ~35-~35: Possible typo: you repeated a word.
Context: ...tory. While tags.yml will be detected as as a FileChanged event and Pipelines will ...

(ENGLISH_WORD_REPEAT_RULE)


[style] ~66-~66: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ands like terragrunt stack generate. This is a break-glass feature flag and can b...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 markdownlint-cli2 (0.17.2)
docs/2.0/reference/pipelines/feature-flags.md

8-8: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


29-29: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Validate generated content
  • GitHub Check: validate_build
🔇 Additional comments (2)
docs/2.0/reference/pipelines/feature-flags.md (1)

1-4: Title and introduction are clear
The main heading and introductory paragraph effectively explain feature flags and link to the correct HCL/YAML env-block references.

sidebars/reference.js (1)

56-60: Sidebar entry added correctly
The new “Feature Flags” doc link is properly formatted under the “Gruntwork Pipelines” section and points to the correct ID. No changes needed here.

Comment on lines +28 to +36
E.g. given a repository containing the following files:
```
tags.yml
dir1/terragrunt.hcl
dir1/myvars.json
```

When this flag is enabled Pipelines will detect changes to `dir1/myvars.json` as a ModuleChanged for `dir1` and run Terragrunt Plan/Apply for this directory. While `tags.yml` will be detected as as a FileChanged event and Pipelines will run Terragrunt with [queue-include-units-reading](https://terragrunt.gruntwork.io/docs/reference/cli-options/#queue-include-units-reading) for this file.

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Specify code block language & clean up grammar

  • Annotate the fenced block with a language (e.g., ```text) for proper rendering.
  • Add a comma after “When this flag is enabled,” for readability.
  • Remove the duplicated “as” in “detected as as a FileChanged event.”
🧰 Tools
🪛 LanguageTool

[typographical] ~35-~35: It seems that a comma is missing.
Context: ...dir1/myvars.json ``` When this flag is enabled Pipelines will detect changes to `dir1/...

(IF_COMMA)


[duplication] ~35-~35: Possible typo: you repeated a word.
Context: ...tory. While tags.yml will be detected as as a FileChanged event and Pipelines will ...

(ENGLISH_WORD_REPEAT_RULE)

🪛 markdownlint-cli2 (0.17.2)

29-29: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

Comment on lines +6 to +7
## Available Flags

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix heading level jump
You have an h2 (## Available Flags) followed immediately by h4 (####) for each flag. Markdown lint requires stepping one level at a time. Please change each flag heading from #### to ###.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
docs/2.0/reference/pipelines/ignore-filter.md (4)

7-12: Refine wildcard syntax descriptions
The Syntax bullets can be made clearer and more consistent. For example:

- - `:` Is used as a separator between filters
- - `*` Matches any character except `/`, for matches within a specific directory.
- - `**` Matches any character, for matches across multiple directories.
+ - `:` is used as a separator between patterns.
+ - `*` matches any sequence of characters except `/`, within a single directory.
+ - `**` matches any sequence of characters, including `/`, across multiple directory levels.
🧰 Tools
🪛 LanguageTool

[grammar] ~9-~9: This sentence seems to be incomplete. Insert a noun before ‘Is’ to make the sentence complete.
Context: ... separated by the : character. - : Is used as a separator between filters - `...

(MISSING_SUBJECT)


15-20: Use bullet list for specific-file examples
Formatting each pattern example as a Markdown list improves readability:

### Ignore specific files

- `myfile.yml` — Matches the exact path to this file at the root level.
- `myfile.yml:a/b/c/myfile.yml` — Matches both of these specific paths.

21-24: Add missing article in heading
For grammatical correctness, include “the” in the heading:

- ### Ignore all files with extension .md
+ ### Ignore all files with the .md extension
🧰 Tools
🪛 LanguageTool

[uncategorized] ~21-~21: You might be missing the article “the” here.
Context: ...em with :. ### Ignore all files with extension .md **.md - Matches all paths ending...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


33-36: Add missing article in directory-specific extension example
Include “the” in this heading too:

- ### Ignore all files with extension .md in a directory
+ ### Ignore all files with the .md extension in a directory
🧰 Tools
🪛 LanguageTool

[uncategorized] ~33-~33: You might be missing the article “the” here.
Context: ... be ignored. ### Ignore all files with extension .md in a directory docs/**.md - Matc...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0f288b3 and 39553cb.

📒 Files selected for processing (3)
  • custom-dictionary.txt (1 hunks)
  • docs/2.0/reference/pipelines/ignore-filter.md (1 hunks)
  • sidebars/reference.js (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • custom-dictionary.txt
🚧 Files skipped from review as they are similar to previous changes (1)
  • sidebars/reference.js
🧰 Additional context used
🪛 LanguageTool
docs/2.0/reference/pipelines/ignore-filter.md

[grammar] ~9-~9: This sentence seems to be incomplete. Insert a noun before ‘Is’ to make the sentence complete.
Context: ... separated by the : character. - : Is used as a separator between filters - `...

(MISSING_SUBJECT)


[uncategorized] ~21-~21: You might be missing the article “the” here.
Context: ...em with :. ### Ignore all files with extension .md **.md - Matches all paths ending...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


[uncategorized] ~33-~33: You might be missing the article “the” here.
Context: ... be ignored. ### Ignore all files with extension .md in a directory docs/**.md - Matc...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Validate generated content
  • GitHub Check: Pull Request has non-contributor approval
  • GitHub Check: validate_build
🔇 Additional comments (5)
docs/2.0/reference/pipelines/ignore-filter.md (5)

1-2: Title is clear and consistent
The page title “Pipelines Ignore Filter” follows the same Title Case convention as “Feature Flags” and concisely describes the feature.


3-4: Verify HCL/YAML reference links
Please confirm that the [HCL](/2.0/reference/pipelines/configurations-as-code/api#env-block) and [YAML](/2.0/reference/pipelines/configurations#env) links resolve correctly in your documentation site.


25-28: README.md example is clear
The pattern

README.md:**/README.md

effectively shows how to ignore both the root README.md and any nested README.md files.


29-32: Directory-wide ignore example is clear
The a/** pattern correctly demonstrates ignoring all files within a directory and its subdirectories.


37-41: Examples look good
The final example (a/*) is well explained and aligns with the other patterns.

@Resonance1584 Resonance1584 changed the title [WIP] Add Feature Flags docs Add Feature Flags docs May 12, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (3)
docs/2.0/reference/pipelines/ignore-filter.md (3)

9-11: Unify bullet list grammar and punctuation
The three syntax bullets are inconsistent in capitalization and punctuation. For clarity and consistency, consider rephrasing as follows:

- - `,` Is used as a separator between filters
- - `*` Matches any character except `/`, for matches within a specific directory.
- - `**` Matches any character, for matches across multiple directories.
+ - `,`: used to separate multiple patterns.
+ - `*`: matches any character except `/` within a single directory segment.
+ - `**`: matches any character across multiple directory segments.
🧰 Tools
🪛 LanguageTool

[grammar] ~9-~9: This sentence seems to be incomplete. Insert a noun before ‘Is’ to make the sentence complete.
Context: ... separated by the , character. - , Is used as a separator between filters - `...

(MISSING_SUBJECT)


21-23: Add missing article for clarity
The header is missing “the” before “extension”:

- ### Ignore all files with extension .md
+ ### Ignore all files with the extension `.md`
🧰 Tools
🪛 LanguageTool

[uncategorized] ~21-~21: You might be missing the article “the” here.
Context: ...em with ,. ### Ignore all files with extension .md **.md - Matches all paths ending...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


33-36: Add missing article and inline code formatting
Similarly, prepend “the” in this header and wrap .md in backticks:

- ### Ignore all files with extension .md in a directory
+ ### Ignore all files with the extension `.md` in a directory
🧰 Tools
🪛 LanguageTool

[uncategorized] ~33-~33: You might be missing the article “the” here.
Context: ... be ignored. ### Ignore all files with extension .md in a directory docs/**.md - Matc...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 39553cb and a2b4f45.

📒 Files selected for processing (1)
  • docs/2.0/reference/pipelines/ignore-filter.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/2.0/reference/pipelines/ignore-filter.md

[grammar] ~9-~9: This sentence seems to be incomplete. Insert a noun before ‘Is’ to make the sentence complete.
Context: ... separated by the , character. - , Is used as a separator between filters - `...

(MISSING_SUBJECT)


[uncategorized] ~21-~21: You might be missing the article “the” here.
Context: ...em with ,. ### Ignore all files with extension .md **.md - Matches all paths ending...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


[uncategorized] ~33-~33: You might be missing the article “the” here.
Context: ... be ignored. ### Ignore all files with extension .md in a directory docs/**.md - Matc...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Pull Request has non-contributor approval
  • GitHub Check: validate_build
  • GitHub Check: Validate generated content

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

♻️ Duplicate comments (2)
docs/2.0/reference/pipelines/feature-flags.md (2)

8-8: Fix heading level jump

The document uses level-4 headings (####) for each flag immediately under an H2 (## Available Flags). Markdown best practices require stepping one level at a time—please convert these to level-3 headings (###).

Also applies to: 21-21, 34-34, 58-58, 73-73, 88-88

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

8-8: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


46-46: 🛠️ Refactor suggestion

Fix duplicated word and add missing comma

There's a double "as" and a missing comma for clarity. Consider rewriting the sentence:

- When this flag is enabled Pipelines will detect changes to `dir1/myvars.json` as a ModuleChanged for `dir1` and run Terragrunt Plan/Apply for this directory. While `tags.yml` will be detected as as a FileChanged event and Pipelines will run Terragrunt with [queue-include-units-reading](https://terragrunt.gruntwork.io/docs/reference/cli-options/#queue-include-units-reading) for this file.
+ When this flag is enabled, Pipelines will detect changes to `dir1/myvars.json` as a ModuleChanged job for `dir1` and run Terragrunt Plan/Apply accordingly. Meanwhile, `tags.yml` will be detected as a FileChanged event and Pipelines will run Terragrunt with [queue-include-units-reading](https://terragrunt.gruntwork.io/docs/reference/cli-options/#queue-include-units-reading) for that file.
🧰 Tools
🪛 LanguageTool

[typographical] ~46-~46: It seems that a comma is missing.
Context: ...dir1/myvars.json ``` When this flag is enabled Pipelines will detect changes to `dir1/...

(IF_COMMA)


[duplication] ~46-~46: Possible typo: you repeated a word.
Context: ...tory. While tags.yml will be detected as as a FileChanged event and Pipelines will ...

(ENGLISH_WORD_REPEAT_RULE)

🧹 Nitpick comments (3)
docs/2.0/reference/pipelines/ignore-list.md (2)

9-9: Fix grammar in comma-separator bullet
Change "- , Is used as a separator between filters" to something like:

- `,` Is used as a separator between filters
+ The `,` character is used to separate multiple filter patterns.
🧰 Tools
🪛 LanguageTool

[grammar] ~9-~9: This sentence seems to be incomplete. Insert a noun before ‘Is’ to make the sentence complete.
Context: ... separated by the , character. - , Is used as a separator between filters - `...

(MISSING_SUBJECT)


10-11: Ensure consistency in bullet phrasing
For uniformity, consider starting each bullet with “The” and using parallel verb forms. For example:

- `*` Matches any character except `/`, for matches within a specific directory.
- `**` Matches any character, for matches across multiple directories.
+ The `*` pattern matches any character except `/` (within a single directory).
+ The `**` pattern matches any character across multiple directory levels.
docs/2.0/reference/pipelines/feature-flags.md (1)

26-26: Add missing comma before "but" for consistency

Several flag descriptions use:

"This behavior will likely become the default in a major release of Pipelines but is currently opt-in…"

Please insert a comma before "but" in each occurrence:

- ...release of Pipelines but is currently opt-in...
+ ...release of Pipelines, but is currently opt-in...

This applies to lines 26, 48, and 63.

Also applies to: 48-48, 63-63

🧰 Tools
🪛 LanguageTool

[uncategorized] ~26-~26: Possible missing comma found.
Context: ... default in a major release of Pipelines but is currently opt-in due to being a brea...

(AI_HYDRA_LEO_MISSING_COMMA)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a2b4f45 and a8943e3.

📒 Files selected for processing (5)
  • docs/2.0/reference/pipelines/configurations-as-code/api.md (1 hunks)
  • docs/2.0/reference/pipelines/configurations.md (1 hunks)
  • docs/2.0/reference/pipelines/feature-flags.md (1 hunks)
  • docs/2.0/reference/pipelines/ignore-list.md (1 hunks)
  • sidebars/reference.js (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • docs/2.0/reference/pipelines/configurations.md
  • docs/2.0/reference/pipelines/configurations-as-code/api.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • sidebars/reference.js
🧰 Additional context used
🪛 LanguageTool
docs/2.0/reference/pipelines/feature-flags.md

[uncategorized] ~26-~26: Possible missing comma found.
Context: ... default in a major release of Pipelines but is currently opt-in due to being a brea...

(AI_HYDRA_LEO_MISSING_COMMA)


[typographical] ~46-~46: It seems that a comma is missing.
Context: ...dir1/myvars.json ``` When this flag is enabled Pipelines will detect changes to `dir1/...

(IF_COMMA)


[duplication] ~46-~46: Possible typo: you repeated a word.
Context: ...tory. While tags.yml will be detected as as a FileChanged event and Pipelines will ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~48-~48: Possible missing comma found.
Context: ... default in a major release of Pipelines but is currently opt-in due to being a brea...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~63-~63: Possible missing comma found.
Context: ... default in a major release of Pipelines but is currently opt-in due to being a brea...

(AI_HYDRA_LEO_MISSING_COMMA)


[style] ~77-~77: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...options/#queue-include-units-reading). This is a break-glass feature flag and can b...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~92-~92: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ands like terragrunt stack generate. This is a break-glass feature flag and can b...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

docs/2.0/reference/pipelines/ignore-list.md

[grammar] ~9-~9: This sentence seems to be incomplete. Insert a noun before ‘Is’ to make the sentence complete.
Context: ... separated by the , character. - , Is used as a separator between filters - `...

(MISSING_SUBJECT)


[uncategorized] ~21-~21: You might be missing the article “the” here.
Context: ...em with ,. ### Ignore all files with extension .md **.md - Matches all paths ending...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


[uncategorized] ~33-~33: You might be missing the article “the” here.
Context: ... be ignored. ### Ignore all files with extension .md in a directory docs/**.md - Matc...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🪛 markdownlint-cli2 (0.17.2)
docs/2.0/reference/pipelines/feature-flags.md

8-8: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


40-40: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Validate generated content
  • GitHub Check: Pull Request has non-contributor approval
  • GitHub Check: validate_build
🔇 Additional comments (7)
docs/2.0/reference/pipelines/ignore-list.md (7)

3-4: Verify the accuracy of documentation links
Please ensure that the [HCL](/2.0/reference/pipelines/configurations-as-code/api#ignore_list) and [YAML](/2.0/reference/pipelines/configurations#ignore-list) anchors actually exist in your generated site and point to the correct sections.


5-8: Looks good: Syntax section and description
The heading and introductory sentence clearly explain the ignore-list configuration.


13-16: Approve Common Examples heading and first example
The “Common Examples” heading and “Ignore specific files” section are clear and correctly formatted.


17-20: Approve specific-files example
The two-path pattern example is correct and the explanatory text is clear.


25-28: Approve README.md ignore example
The combined root and subdirectory README.md pattern is correct and well-explained.


29-32: Approve directory-only ignore example
The a/** pattern and description accurately cover ignoring files in a directory and its subdirectories.


37-40: Approve top-level only ignore example
The a/* pattern correctly conveys that subdirectories are excluded.

Comment on lines +33 to +36
### Ignore all files with extension .md in a directory

`docs/**.md` - Matches all .md files in the docs directory and its subdirectories. For example, `docs/file.md` will be ignored, but not `docs/file.yml`.

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Clarify .md-in-directory example and pattern
For consistency and accuracy, adjust to:

- ### Ignore all files with extension .md in a directory
+ ### Ignore all files with the .md extension in the docs directory

- `docs/**.md` - Matches all .md files in the docs directory and its subdirectories.
+ `docs/**/*.md` - Matches all .md files in the docs directory and its subdirectories.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Ignore all files with extension .md in a directory
`docs/**.md` - Matches all .md files in the docs directory and its subdirectories. For example, `docs/file.md` will be ignored, but not `docs/file.yml`.
### Ignore all files with the .md extension in the docs directory
`docs/**/*.md` - Matches all .md files in the docs directory and its subdirectories. For example, `docs/file.md` will be ignored, but not `docs/file.yml`.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~33-~33: You might be missing the article “the” here.
Context: ... be ignored. ### Ignore all files with extension .md in a directory docs/**.md - Matc...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🤖 Prompt for AI Agents
In docs/2.0/reference/pipelines/ignore-list.md around lines 33 to 36, clarify
the example and pattern for ignoring .md files in a directory by adjusting the
explanation to accurately reflect that the pattern `docs/**/*.md` matches all
.md files in the docs directory and all its subdirectories, ensuring consistency
and correctness in the description.

Comment on lines +21 to +24
### Ignore all files with extension .md

`**.md` - Matches all paths ending in .md, regardless of directory depth.

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Clarify .md extension example and pattern
The heading and pattern can be more precise. Update as follows:

- ### Ignore all files with extension .md
+ ### Ignore all files with the .md extension

- `**.md` - Matches all paths ending in .md, regardless of directory depth.
+ `**/*.md` - Matches all paths ending in .md, regardless of directory depth.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Ignore all files with extension .md
`**.md` - Matches all paths ending in .md, regardless of directory depth.
### Ignore all files with the .md extension
`**/*.md` - Matches all paths ending in .md, regardless of directory depth.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~21-~21: You might be missing the article “the” here.
Context: ...em with ,. ### Ignore all files with extension .md **.md - Matches all paths ending...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🤖 Prompt for AI Agents
In docs/2.0/reference/pipelines/ignore-list.md around lines 21 to 24, clarify
the example and pattern for ignoring .md files by updating the heading to
explicitly mention ignoring all files with the .md extension and revise the
pattern to use a more precise glob pattern like '**/*.md' to match all markdown
files at any directory depth.

Comment on lines +40 to +44
```
tags.yml
dir1/terragrunt.hcl
dir1/myvars.json
```
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Specify fenced code block language

The sample file layout is wrapped in a fenced code block without a language identifier. Add one (e.g., text) so markdown linting passes and rendering is correct.

- ```
+ ```text
 tags.yml
 dir1/terragrunt.hcl
 dir1/myvars.json
- ```
+ ```
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

40-40: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In docs/2.0/reference/pipelines/feature-flags.md around lines 40 to 44, the
fenced code block showing the sample file layout lacks a language identifier,
which can cause markdown linting issues and improper rendering. Add a language
specifier like "text" immediately after the opening triple backticks to fix
this, so the block starts with ```text instead of just ```.

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.

1 participant