fix: add node types#7
Conversation
📝 WalkthroughWalkthroughThis PR updates build infrastructure and TypeScript configuration. The CI workflow is enhanced to skip unnecessary runs when only documentation files change, and TypeScript is configured to include Node.js type definitions for improved type checking. ChangesConfiguration Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/ci.yml:
- Around line 9-11: Update the paths-ignore entries that currently use the glob
'.github/*.md' to '.github/**/*.md' so markdown files in nested .github
subdirectories are ignored; specifically modify the on.pull_request.paths-ignore
and on.push.paths-ignore entries to replace '.github/*.md' with
'.github/**/*.md'.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: d9e08c89-7176-4dd5-9adf-bb0316cbb2c1
📒 Files selected for processing (2)
.github/workflows/ci.ymltsconfig.json
| - '**.md' | ||
| - 'docs/**' | ||
| - '.github/*.md' |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What is the correct glob syntax for GitHub Actions paths-ignore to match Markdown files recursively (all subdirectories)?
💡 Result:
To recursively match and ignore all Markdown files in a repository using GitHub Actions paths-ignore syntax, use the following glob pattern: '/.md' Explanation: - The `` (globstar) pattern matches any number of directories and subdirectories recursively [1][2]. - The *.md part ensures that all files ending with the `.md` extension are matched [2]. - When used within the `paths-ignore` key, this pattern tells GitHub Actions to skip triggering the workflow if any of the files modified in a push or pull request match this pattern [3]. Example configuration: on: push: paths-ignore: - '/.md' This configuration will prevent the workflow from running if only Markdown files are changed [3]. If you need to include other files while ignoring Markdown, you can list them as well, or use the `paths` filter with negative patterns (e.g., '!/*.md') if you prefer a single inclusion/exclusion list [3][2].
Citations:
- 1: https://github.com/actions/toolkit/tree/main/packages/glob
- 2: https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md
- 3: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
🌐 Web query:
GitHub Actions workflow paths-ignoreglobstar pattern: is'/.md'valid/recommended for matching markdown in subdirectories, or is'/.md'/'.md' the correct/accepted form? Provide official docs/examples.
💡 Result:
For GitHub Actions paths-ignore and paths filters, the correct and recommended pattern to match all Markdown files in a repository, including those in subdirectories, is '/*.md' [1][2]. Official GitHub documentation specifies that the wildcard matches any number of directories and files recursively, including directory separators [1]. Here is a breakdown of the patterns: - `'/*.md'`: This is the correct, standard approach. The ensures recursive matching across any subdirectory depth, and the *.md matches the file extension [1]. - '/*.md': Matches README.md, docs/setup.md, and src/components/button/readme.md [1]. - '*.md': Only matches Markdown files in the root directory of the repository [1]. - '.md': While sometimes interpreted by specific glob implementations, it is not the recommended syntax for GitHub Actions workflows. Using the explicit '/*.md' is the standard, documented practice to ensure consistency across different OS environments and actions [1][3]. Patterns in GitHub Actions are checked sequentially [1]. You can also use negations (the ! character) if you need to include specific files while ignoring others [1][4]. Example configuration for a workflow: on: push: paths-ignore: - '/*.md' This configuration will prevent the workflow from triggering when only Markdown files are modified in your repository [1][2].
Citations:
- 1: https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md
- 2: https://stackoverflow.com/questions/70478320/github-actions-ignore-certain-files-inside-a-directory
- 3: https://github.com/marketplace/actions/glob-match
- 4: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
🌐 Web query:
GitHub Actions paths-ignorepattern to ignore Markdown files under a specific directory (e.g.,.github/), including nested subdirectories—what is the correct glob?
💡 Result:
To ignore all Markdown files within a specific directory (such as.github/) and all of its nested subdirectories, use the following glob pattern in your GitHub Actions workflow file [1][2]: - '.github//*.md' This pattern works as follows: -.github/ specifies the target directory [1]. - matches any directory or subdirectory depth [1][3]. - .md matches all files ending with the.md extension [1][3]. For example, your workflow configuration would look like this: on: push: paths-ignore: - '.github//.md' This configuration ensures that changes to any Markdown file located anywhere within the.github/ directory tree will not trigger the workflow [2]. Important notes on GitHub Actions path filtering: 1. Glob Syntax: The wildcard is essential for matching nested paths [1][3]. Using a single * would only match files in the immediate directory, excluding those in subdirectories [1][3]. 2. Root Paths: Patterns in GitHub Actions are evaluated relative to the repository root [1][3]. 3. Exclusivity: You cannot use both paths and paths-ignore for the same event in a single workflow [2][4]. If you need to combine inclusion and exclusion logic, use the paths filter and prefix your exclusion patterns with the! character [2].
Citations:
- 1: https://www.codegenes.net/blog/github-actions-ignore-certain-files-inside-a-directory/
- 2: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 3: https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md
- 4: https://github.github.io/actions-cheat-sheet/actions-cheat-sheet.html
🌐 Web query:
Find GitHub Actions official documentation or examples for paths-ignoreglob patterns to recursively ignore Markdown under.github/, specifically whether to use .github//.mdvs.github/.mdvs/.mdor/.md.
💡 Result:
To recursively ignore all Markdown (.md) files within the .github/ directory and its subdirectories in GitHub Actions, you should use the pattern: .github//*.md This pattern is the correct choice because: 1. .github//*.md: The globstar matches any directory level (recursively) within the `.github/` folder, effectively capturing all `.md` files in `.github/` and any deeper subdirectories like `.github/workflows/docs/file.md` [1][2]. 2. `.github/*.md`: This only matches Markdown files located directly in the root of the `.github/` directory. It does not look into subdirectories [2]. 3. `/*.md`: This matches all Markdown files in the entire repository, not just those within `.github/` [2]. 4. `/*.md`: This matches only Markdown files in the repository root [2]. For your workflow configuration, you would use this under the `paths-ignore` key: on: push: paths-ignore: - '.github//*.md' GitHub Actions glob patterns are standard, where `*` matches any character (except directory separators) and matches any number of directories [1][9]. If you need to ignore Markdown files globally throughout the repository, you would use /*.md instead [3][2].
Citations:
- 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 2: https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md
- 3: https://stackoverflow.com/questions/70478320/github-actions-ignore-certain-files-inside-a-directory
🌐 Web query:
Search GitHub Actions docs/examples for paths-ignoreglob patterns specifically for recursive markdown: examples of/*.mdand.github//*.md.
💡 Result:
In GitHub Actions, the paths-ignore filter supports glob patterns to recursively match markdown files across a repository [1]. To ignore all markdown files (.md) regardless of their location, you can use the /*.md pattern [2][3]. The double asterisk () wildcard is a globstar that matches any character, including directory separators, allowing the pattern to traverse all subdirectories [3][1]. Examples for `paths-ignore` usage: Ignore all markdown files in the repository: on: push: paths-ignore: - '/*.md' Ignore all markdown files specifically within the `.github` directory and its subdirectories: on: push: paths-ignore: - '.github//*.md' As documented, the wildcard matches any character including slashes, effectively acting as a recursive search [9][10]. When using these patterns, note that if any changed files do not match your paths-ignore patterns, the workflow will trigger [10]. If you intend to use both inclusion (paths) and exclusion (paths-ignore) logic, you cannot use them simultaneously in the same event; instead, use paths and prepend the exclusion patterns with the ! character (e.g., - '!/*.md') [1].
Citations:
- 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 2: https://stackoverflow.com/questions/70478320/github-actions-ignore-certain-files-inside-a-directory
- 3: https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md
🌐 Web query:
GitHub Actions workflow syntaxdocs section onpaths-ignore—what example pattern do they give to ignore all *.mdfiles (including nested)? Also confirm the correct recursive pattern for files under.github/(e.g.,.github/**/).
💡 Result:
To ignore all .md files (including those in nested directories) in GitHub Actions, you should use the recursive glob pattern '/.md' [1][2]. The '' wildcard is the correct recursive pattern in GitHub Actions, matching zero or more directories, including the repository root and any depth of subdirectories [1][3]. Regarding your question about recursive patterns for the.github/ directory (e.g., to ignore all files under.github/), the correct pattern is '.github/' [3][4][5]. Using this pattern ensures that all files within the.github/ folder and all of its subdirectories are matched [1][3]. Summary of key patterns: - All Markdown files: '/.md' [2] - Everything within the.github directory: '.github/' [3][5] Note that GitHub Actions' path filters operate relative to the repository root [1][2]. If you use a pattern like '.md', it will only match Markdown files in the root directory, which is why the leading '/' is necessary to achieve a recursive effect [1][2].
Citations:
- 1: https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md
- 2: https://www.codegenes.net/blog/github-actions-ignore-certain-files-inside-a-directory/
- 3: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 4: on.pull_request.paths-ignore are not respected correctly actions/runner#2324
- 5: https://oneuptime.com/blog/post/2025-12-20-path-filtering-github-actions/view
🏁 Script executed:
#!/bin/bash
set -euo pipefail
ls -la .github/workflows || true
sed -n '1,120p' .github/workflows/ci.ymlRepository: FrilLab/frilingo
Length of output: 795
🏁 Script executed:
#!/bin/bash
set -euo pipefail
sed -n '1,160p' .github/workflows/ci.ymlRepository: FrilLab/frilingo
Length of output: 571
🏁 Script executed:
#!/bin/bash
set -euo pipefail
sed -n '1,220p' .github/workflows/ci.ymlRepository: FrilLab/frilingo
Length of output: 571
🏁 Script executed:
#!/bin/bash
set -euo pipefail
nl -ba .github/workflows/ci.yml | sed -n '1,120p'Repository: FrilLab/frilingo
Length of output: 103
🌐 Web query:
site:docs.github.com "paths-ignore" "/*.md" OR site:docs.github.com "paths-ignore" "**/*.md" OR "paths-ignore" ".github/**/*.md"
💡 Result:
The "paths-ignore" key is a configuration option used in GitHub to define file path patterns that should be excluded from specific processes, most notably GitHub Actions workflows and secret scanning [1][2][3]. In GitHub Actions workflows, "paths-ignore" is used within the "on" trigger configuration (for events like "push" or "pull_request") to prevent a workflow from running if the only files modified in a commit or pull request match the ignored patterns [1][4]. It accepts glob patterns using standard wildcards, such as "" and "" [1]. The pattern "/.md" is commonly used to ignore all Markdown files regardless of their location in the repository [5][6][7]. Key points regarding "paths-ignore" in GitHub Actions: - Functionality: If all modified files in a trigger event match the "paths-ignore" patterns, the workflow will not run [1][4]. If at least one file does not match, the workflow will proceed [1][4]. - Syntax: It cannot be used simultaneously with "paths" for the same event in a single workflow configuration [1][4]. To include and exclude paths for the same event, you must use the "paths" filter with the "!" character to negate (exclude) specific patterns [1]. - Glob Patterns: The "" wildcard matches directories recursively, while "" matches files or directories at a specific depth [1][4]. Therefore, "/.md" effectively targets every Markdown file in the entire repository structure [5][7]. Additionally, "paths-ignore" is used in the ".github/secret_scanning.yml" configuration file to exclude specific directories or files from being monitored by GitHub Secret Scanning and push protection [2][8][3]. The same glob pattern rules apply, though it is specifically intended for managing alert suppression rather than workflow execution [2][3].
Citations:
- 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 2: https://docs.github.com/en/enterprise-cloud@latest/code-security/how-tos/secure-your-secrets/customize-leak-detection/excluding-folders-and-files-from-secret-scanning
- 3: https://docs.github.com/en/code-security/how-tos/secure-your-secrets/customize-leak-detection/excluding-folders-and-files-from-secret-scanning
- 4: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 5: https://docs.github.com/en/enterprise-server@3.21/code-security/reference/code-scanning/workflow-configuration-options
- 6: https://docs.github.com/en/enterprise-server@3.19/code-security/reference/code-scanning/workflow-configuration-options
- 7: https://docs.github.com/de/code-security/reference/code-scanning/workflow-configuration-options
- 8: https://docs.github.com/en/enterprise-server@3.13/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/excluding-folders-and-files-from-secret-scanning
🌐 Web query:
site:docs.github.com "paths-ignore" "*.md" "/*.md"
💡 Result:
In GitHub Actions, the paths-ignore filter is used to prevent a workflow from running when changes are limited to specific file paths [1][2]. The patterns you provided behave as follows: 1. ".md": This glob pattern matches any file ending in.md located in the root directory of the repository [1][2]. It does not match.md files inside subdirectories. 2. "/.md": This pattern also matches any file ending in.md in the root directory [1][2]. The leading forward slash is treated as the root directory, making it functionally equivalent to ".md" in the context of repository root path matching. To effectively ignore all markdown files regardless of their location in the repository, you should use the recursive glob pattern: paths-ignore: - '/.md' The double asterisk is the standard way in GitHub Actions workflow syntax to match any number of directories, ensuring that.md files at the root and within any subdirectory are ignored [1][2]. Key considerations: - Workflow triggering: A workflow will run if at least one file in the push or pull request does not match the paths-ignore patterns [1][2]. If all changed files match the patterns in paths-ignore, the workflow will not trigger [1][2]. - Mutually exclusive: You cannot use both paths and paths-ignore for the same event in a single workflow [1][2]. If you need both inclusive and exclusive filtering, use paths with the! operator (e.g., paths: ['src/', '!src//*.md']) [1][2].
Citations:
- 1: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 2: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
🌐 Web query:
site:docs.github.com "paths-ignore" ".github" "md" glob
💡 Result:
In GitHub Actions, the paths-ignore keyword is used to prevent a workflow from running when changes are pushed to specific file paths [1][2]. It accepts glob patterns to match file paths [1][3]. To ignore all Markdown files, you can use the /*.md pattern [4]. If you also want to ignore everything within the .github directory, you can add .github/ to your list [1][5]. Example configuration: on: push: paths-ignore: - '/*.md' - '.github/' Key rules for paths-ignore: - You cannot use paths and paths-ignore in the same workflow for the same event [1][2]. If you need both inclusion and exclusion, use paths with the ! character (e.g., paths: ['src/', '!src/tests/']) [1][6]. - The workflow will run if at least one changed file does not match the paths-ignore patterns [1][2]. - Glob patterns support * (matches zero or more characters, excluding directory separators) and `` (matches zero or more directories) [1][7]. Note: The paths-ignore keyword is also used in other GitHub contexts, such as `secret_scanning.yml` (located at `.github/secret_scanning.yml`), to exclude specific directories or files from secret scanning alerts [8][5].
Citations:
- 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 2: https://docs.github.com/actions/using-workflows/triggering-a-workflow
- 3: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 4: https://docs.github.com/en/enterprise-cloud@latest/code-security/reference/code-scanning/workflow-configuration-options?apiVersion=2022-11-28
- 5: https://docs.github.com/en/enterprise-cloud@latest/code-security/how-tos/secure-your-secrets/customize-leak-detection/excluding-folders-and-files-from-secret-scanning
- 6: https://docs.github.com/fr/enterprise-server@3.15/actions/reference/workflows-and-actions/workflow-syntax
- 7: https://docs.github.com/de/actions/reference/workflows-and-actions/workflow-syntax
- 8: https://docs.github.com/fr/enterprise-server@3.8/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories
🌐 Web query:
site:docs.github.com "paths-ignore" "**/*.md"
💡 Result:
The configuration "paths-ignore": "/.md" is used in GitHub Actions workflow files to prevent a workflow from triggering when the only changes in a push or pull request are to Markdown (.md) files [1][2][3]. Key details include: * Functionality: The "paths-ignore" filter evaluates the files changed in a commit or pull request [2][3]. If every single changed file matches the patterns specified in "paths-ignore"—in this case, any file with an.md extension anywhere in the repository (indicated by the globstar)—the workflow will not run [2][3]. * Trigger Logic: If at least one changed file does not match the ignored pattern, the workflow will trigger [2][3]. * Pattern Syntax: It uses glob patterns [2][4]. The "" syntax means "match any directory or subdirectory," and "/.md" ensures it applies to all files ending in.md [2][3]. * Usage Constraint: You cannot use both "paths" and "paths-ignore" for the same event in a single workflow [2][3]. If you need to both include and exclude specific paths for the same event, you should use the "paths" filter with the "!" prefix to denote exclusions [2][3].
Citations:
- 1: https://docs.github.com/en/code-security/reference/code-scanning/workflow-configuration-options
- 2: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 3: https://docs.github.com/actions/using-workflows/triggering-a-workflow
- 4: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
🌐 Web query:
site:docs.github.com "paths-ignore" "**" "matches any number of directories"
💡 Result:
Yes, the double asterisk glob pattern is used in GitHub Actions paths-ignore (and other path-based filters) to match zero or more directories [1][2][3]. In the context of path filtering, the wildcard is a recursive glob pattern [4]. When used in a path such as docs/, it tells the system to match the specified directory (in this case, docs) and all of its contents, including all files and subdirectories at any depth [1][2]. Key details regarding this pattern include: - Recursive matching: The pattern matches any number of directories, allowing it to cover deeply nested file structures [5][4]. - Usage in paths-ignore: When you include a pattern like docs/ in paths-ignore, any file change located within that directory tree will cause the pattern to match, effectively excluding those changes from triggering the workflow [1][2]. - Official documentation: GitHub explicitly states that the paths and paths-ignore keywords in workflow syntax accept glob patterns using both * and wildcards to match multiple path names [1][3].
Citations:
- 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 2: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 3: https://docs.github.com/enterprise-cloud@latest/actions/using-workflows/triggering-a-workflow
- 4: https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions
- 5: https://docs.github.com/en/code-security/reference/code-scanning/codeql/codeql-cli-manual/resolve-files
🌐 Web query:
site:docs.github.com "paths-ignore:" "/*.md" example
💡 Result:
In GitHub Actions, paths-ignore is a filter used to prevent a workflow from running when changes are made only to specific files [1][2]. Using "/.md" as a pattern in paths-ignore specifically targets Markdown files located at the root of your repository [1][2]. Example Usage To prevent a workflow from running when only root-level Markdown files are changed, you can configure your workflow as follows: on: push: paths-ignore: - '/.md' How it works: 1. Pattern Matching: The filter uses glob patterns [1][2]. A pattern like "/.md" matches any.md file at the top level of the repository [1]. If you intend to ignore Markdown files in all directories (including subdirectories), you should use "/.md" instead [3][2]. 2. Trigger Behavior: If a commit includes changes to files that do not match the paths-ignore patterns, the workflow will run [1][2]. If all changed files match the paths-ignore patterns, the workflow will be skipped [1][2]. 3. Constraints: You cannot use both paths and paths-ignore for the same event in a single workflow [1][2]. If you need both inclusion and exclusion logic, you must use the paths filter and prefix the patterns you wish to exclude with an exclamation mark (!) [1][2]. Top results: [3][1][2]
Citations:
- 1: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 2: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 3: https://docs.github.com/en/code-security/reference/code-scanning/workflow-configuration-options
🌐 Web query:
site:docs.github.com "paths-ignore:" "'**/*.md'" example
💡 Result:
In GitHub Actions workflows, the paths-ignore filter is used to prevent a workflow from running when changes are made only to specific files or directories [1][2][3]. When you use '/.md' as a pattern, the workflow will ignore any pushes or pull requests where only Markdown files are modified [4][5]. Example Usage To configure a workflow to skip execution if only Markdown files are changed, add the following to your workflow YAML file: on: push: paths-ignore: - '/.md' pull_request: paths-ignore: - '/*.md' Important Considerations: 1. Behavior: The workflow will not run if all modified files in the push or pull request match the patterns in paths-ignore [1][2][3]. If even one file is modified that does not match the ignore pattern, the workflow will trigger [1][2][3]. 2. Limitations: You cannot use both paths and paths-ignore for the same event in a single workflow [1][2][3]. If you need to both include and exclude specific paths, use only the paths filter and prefix the excluded paths with the '!' character [1][2][3]. 3. Pattern Syntax: The '' wildcard matches nested directories, ensuring that all Markdown files throughout the entire repository are ignored [1][2][3].
Citations:
- 1: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 2: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 3: https://docs.github.com/actions/using-workflows/triggering-a-workflow
- 4: https://docs.github.com/en/code-security/reference/code-scanning/workflow-configuration-options
- 5: https://docs.github.com/en/enterprise-server@3.21/code-security/reference/code-scanning/workflow-configuration-options
🌐 Web query:
site:docs.github.com "paths-ignore:" "'**.md'" example
💡 Result:
In GitHub Actions, the paths-ignore keyword is used to prevent a workflow from running when changes are limited to specific file paths or patterns [1][2]. The pattern '/*.md' effectively matches all files with a .md extension in any directory within the repository [1][2]. ### Example Usage To prevent a workflow from running when only Markdown files are changed, you can use the following configuration in your workflow YAML file [3][2]: yaml on: push: paths-ignore: - '/*.md' pull_request: paths-ignore: - '/*.md' ### Key Behaviors * Pattern Matching: The `` syntax is a glob wildcard that matches zero or more directories, ensuring that all Markdown files throughout the repository are ignored [1][2]. * Trigger Logic: If a push or pull request includes files that do not match the paths-ignore patterns, the workflow will still run [1][2]. The workflow only skips if all changed files are covered by the defined `paths-ignore` patterns [1][2]. * Exclusive Usage: You cannot use both `paths` and `paths-ignore` for the same event in a single workflow [1][2]. If you need to both include and exclude specific paths for the same event, use `paths` with the `!` (exclamation mark) character to prefix excluded paths [1][2]. For example, to run a workflow on all files except Markdown files and specific documentation files, you could use: yaml on: push: paths: - '.js' - '!docs/*.md'
Citations:
- 1: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 2: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 3: https://docs.github.com/en/code-security/reference/code-scanning/workflow-configuration-options
🌐 Web query:
site:docs.github.com "paths-ignore" ".github/**/*.md"
💡 Result:
In GitHub Actions, the paths-ignore filter is used to prevent a workflow from running when changes are made to specific file paths [1][2]. The pattern.github//.md is a valid glob pattern that instructs GitHub Actions to ignore changes to any Markdown files located within the.github directory or any of its subdirectories [1][3]. Key points regarding the use of paths-ignore: - Functionality: If all file changes in a push or pull request match the patterns listed in paths-ignore, the workflow will not run [1][3]. If at least one changed file does not match the paths-ignore patterns, the workflow will run [1][2]. - Syntax: The paths-ignore keyword accepts glob patterns, including the wildcard, which matches zero or more directories [1][2]. - Constraints: You cannot use paths and paths-ignore filters for the same event in a single workflow [1][3]. If you need to both include and exclude specific paths, you should use the paths filter combined with the! character to explicitly exclude files [1][4]. - Example configuration: on: push: paths-ignore: - '.github//.md' This configuration ensures that modifications to Markdown files within the.github directory do not trigger the workflow [1][2].
Citations:
- 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 2: https://docs.github.com/actions/using-workflows/triggering-a-workflow
- 3: http://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow
- 4: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
🌐 Web query:
site:docs.github.com "paths-ignore" ".github/**" ".md"
💡 Result:
In GitHub Actions, the paths-ignore filter is used to prevent a workflow from running when changes are made only to specific files or directories [1][2]. The filter uses glob patterns to match file paths [1][3]. To ignore all files within the.github directory and any files ending in.md, you would configure your workflow trigger as follows: on: push: paths-ignore: - '.github/' - '/.md' Key points regarding this configuration: - Glob Patterns: The wildcard is used to match nested directories [1]. For.md files, using /.md ensures that markdown files are ignored regardless of their depth in the repository [4]. - Trigger Behavior: If all changed files in a push or pull request match the patterns defined in paths-ignore, the workflow will not run [1][2]. If at least one file is changed that does not match these patterns, the workflow will trigger [1][2]. - Exclusion Only: You cannot use both paths and paths-ignore for the same event in a workflow [1][5]. If you need to both include and exclude paths simultaneously, you must use the paths filter and prefix the exclusion patterns with the! character (e.g., - 'src/' and - '!src//*.md') [1][2].
Citations:
- 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
- 2: https://docs.github.com/actions/using-workflows/triggering-a-workflow
- 3: https://docs.github.com/en/enterprise-server@3.0/articles/workflow-syntax-for-github-actions
- 4: https://docs.github.com/en/enterprise-server@3.21/code-security/reference/code-scanning/workflow-configuration-options
- 5: http://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow
🏁 Script executed:
#!/bin/bash
set -euo pipefail
url="https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions"
curl -L -s "$url" | rg -n "paths-ignore|paths:\\s*|\\*\\*/\\*\\.md|\\*/\\*\\.md|\\.github/\\*\\*/\\*\\.md|\\.github/\\*\\.md|\\*\\.md" || trueRepository: FrilLab/frilingo
Length of output: 50373
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Try a second doc section that sometimes contains triggering examples
url="https://docs.github.com/actions/using-workflows/triggering-a-workflow"
curl -L -s "$url" | rg -n "paths-ignore|\\*\\*/\\*\\.md|\\*/\\*\\.md|\\.github/\\*\\*/\\*\\.md|\\.github/\\*\\.md" || trueRepository: FrilLab/frilingo
Length of output: 50373
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Fetch raw HTML and extract small matching windows for better context
url="https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions"
html="$(curl -L -s "$url")"
printf "%s" "$html" | rg -n "paths-ignore.{0,200}" | head -n 20 || trueRepository: FrilLab/frilingo
Length of output: 50373
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Grep for any literal '**/*.md' occurrence
url="https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions"
html="$(curl -L -s "$url")"
printf "%s" "$html" | rg -n "\\*\\*/\\*\\.md" || trueRepository: FrilLab/frilingo
Length of output: 50373
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Grep for any literal '.github/**/*.md' occurrence
url="https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions"
html="$(curl -L -s "$url")"
printf "%s" "$html" | rg -n "\\.github/\\*\\*/\\*\\.md" || trueRepository: FrilLab/frilingo
Length of output: 42
Fix .github markdown ignore glob to include subdirectories in paths-ignore.
Change '.github/*.md' to '.github/**/*.md' in both on.pull_request.paths-ignore and on.push.paths-ignore. Leave '**.md' as-is since it already matches .md files anywhere in the repo.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/ci.yml around lines 9 - 11, Update the paths-ignore
entries that currently use the glob '.github/*.md' to '.github/**/*.md' so
markdown files in nested .github subdirectories are ignored; specifically modify
the on.pull_request.paths-ignore and on.push.paths-ignore entries to replace
'.github/*.md' with '.github/**/*.md'.
2 participants
Summary
Add tsconfig.json's types - node
Type of Change
Summary by CodeRabbit