Skip to content

fix glob pattern for impacted projects #1989

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 1 commit into from
Jun 18, 2025

Conversation

motatoes
Copy link
Contributor

@motatoes motatoes commented Jun 18, 2025

fix for #1988

Summary by CodeRabbit

  • Bug Fixes
    • Updated how modified projects are detected to improve accuracy when project directories are set to the current directory (".").
  • Tests
    • Added a new test to ensure projects with the current directory as their path are correctly handled when identifying impacted projects.

Copy link
Contributor

coderabbitai bot commented Jun 18, 2025

Walkthrough

The changes update the logic in the GetModifiedProjects method to always use a non-recursive glob pattern when matching project directories, regardless of project type. Additionally, a new test is introduced to verify that projects with the directory set to "." are not incorrectly marked as impacted by changes in subdirectories.

Changes

File(s) Change Summary
libs/digger_config/digger_config.go Simplified include pattern logic in GetModifiedProjects to always use non-recursive glob.
libs/digger_config/digger_config_test.go Added test for projects with "." as directory, ensuring correct impact detection behavior.

Poem

In the warren of code, a pattern was found,
Where globs once wandered recursively around.
Now, with a hop, the logic is neat—
Only direct paths do projects now greet.
A bunny test checks the dot with delight,
Ensuring subfolders stay out of sight!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch fix/glob-pattern-for-impacted-projects

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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 auto-generate unit tests to generate unit tests for 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

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Simplifies and fixes the glob pattern matching logic in project impact detection, particularly affecting how changed files are matched against project directories.

  • Modified libs/digger_config/digger_config.go to use a consistent * glob pattern for both Terragrunt and non-Terragrunt projects, simplifying the path matching logic
  • Added test in libs/digger_config/digger_config_test.go to verify correct behavior when project directory is set to '.' to prevent false matches from subdirectories

2 files reviewed, no comments
Edit PR Review Bot Settings | Greptile

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

🔭 Outside diff range comments (2)
libs/digger_config/digger_config.go (2)

865-872: ‘./*’ pattern misses root-level files when project.Dir == "."

filepath.Join(project.Dir, "*") evaluates to "./*" for dot-projects.
Changed files that live at the repository root (e.g. "main.tf") will not match "./*" because they do not start with "./".
As a result, a project whose Dir is "." will never be marked as impacted by root-level changes – an obvious regression compared to the previous recursive behaviour.

- includePatterns = append(includePatterns, filepath.Join(project.Dir, "*"))
+ if project.Dir == "." || project.Dir == "" {
+     includePatterns = append(includePatterns, "*")          // match root-level files
+ } else {
+     includePatterns = append(includePatterns, filepath.Join(project.Dir, "*"))
+ }

Please add a companion test proving that a root-level change (e.g. "main.tf") does impact a "." project.


861-870: Repeatedly appending the same pattern inside the inner loop inflates includePatterns

includePatterns is re-initialised for every changed file, then appended to: over N files the base pattern is added N times, growing the slice quadratically and doing redundant work during pattern matching.

Move the construction of includePatterns outside the for _, changedFile := … loop:

- for _, changedFile := range changedFiles {
-     includePatterns := project.IncludePatterns
-     excludePatterns := project.ExcludePatterns
-     includePatterns = append(includePatterns, ...)
-     ...
- }
+ includePatterns := append(
+     slices.Clone(project.IncludePatterns),          // keep original slice intact
+     filepath.Join(project.Dir, "*"),
+ )
+ excludePatterns := project.ExcludePatterns
+
+ for _, changedFile := range changedFiles {
+     if MatchIncludeExcludePatternsToFile(changedFile, includePatterns, excludePatterns) {
+         ...
+     }
+ }

This removes needless allocations and comparisons while retaining behaviour.

🧹 Nitpick comments (1)
libs/digger_config/digger_config_test.go (1)

1270-1285: Test misses root-level change & contains dead code

  1. The new test proves that sub-directory changes do not impact a dot-project, but it does not prove that root-level changes do.
    Please extend the test (or add a second one) with changedFiles := []string{"main.tf"} and assert one impacted project.

  2. Lines 1281-1282 contain a commented-out variable declaration that can be safely removed.

-    //expectedImpactingLocations := map[string]ProjectToSourceMapping{}

Cleaning this up keeps the suite tidy and focused.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f89f081 and 822f46d.

📒 Files selected for processing (2)
  • libs/digger_config/digger_config.go (1 hunks)
  • libs/digger_config/digger_config_test.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (10)
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build
  • GitHub Check: Build

@motatoes motatoes merged commit 474d3d0 into develop Jun 18, 2025
12 checks passed
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