Skip to content

ci(docker): add path filters to avoid unnecessary builds - #30

Merged
louisdevzz merged 1 commit into
mainfrom
fix/docker-and-install
Mar 4, 2026
Merged

louisdevzz merged 1 commit into
mainfrom
fix/docker-and-install

Conversation

@louisdevzz

@louisdevzz louisdevzz commented Mar 4, 2026 •

Copy link
Copy Markdown
Contributor

Only trigger Docker build when code actually changes:

  • Rust source code (src/, crates/, benches/)
  • Dependencies (Cargo.toml, Cargo.lock)
  • Docker configuration (Dockerfile, .dockerignore)

Skip build for:

  • Documentation changes (*.md, docs/)
  • CI workflow updates (docker-publish.yml itself)
  • Other non-code files

This saves GitHub Actions minutes and avoids waste builds.

Summary by CodeRabbit

Chores

  • Optimized Docker publish workflow to trigger selectively—only when source code, dependencies, or Docker configuration changes occur. Documentation changes no longer trigger unnecessary builds, reducing CI/CD overhead and providing faster feedback on pull requests.

Only trigger Docker build when code actually changes:

- Rust source code (src/, crates/, benches/)

- Dependencies (Cargo.toml, Cargo.lock)

- Docker configuration (Dockerfile, .dockerignore)

Skip build for:

- Documentation changes (*.md, docs/)

- CI workflow updates (docker-publish.yml itself)

- Other non-code files

This saves GitHub Actions minutes and avoids waste builds.
@louisdevzz
louisdevzz merged commit 858f96a into main Mar 4, 2026
4 of 8 checks passed
@github-actions github-actions Bot added the ci label Mar 4, 2026
@github-actions

github-actions Bot commented Mar 4, 2026

Copy link
Copy Markdown

PR Intake Checks - Warnings (non-blocking)

The following are recommendations:

  • Missing sections: Summary, Problem statement, Proposed solution, Acceptance criteria
  • No issue reference found (recommended for traceability)

@coderabbitai

coderabbitai Bot commented Mar 4, 2026 •

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'version', 'tests', 'ignore'
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • 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
ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: afb87890-81f4-4d34-9930-6e81e4a61340

📥 Commits

Reviewing files that changed from the base of the PR and between 85a15f5 and c5c871d.

📒 Files selected for processing (1)
  • .github/workflows/docker-publish.yml

Walkthrough

The Docker publish GitHub Actions workflow now includes path filters on push and pull_request triggers. Workflow runs are activated only when changes occur in source directories (src/, crates/, benches/), Cargo configuration files, or Docker-related files, while excluding documentation and Markdown changes.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow Configuration
.github/workflows/docker-publish.yml
Added path filters to push and pull_request triggers to limit workflow execution to code and build-related changes (src/, crates/, benches/, Cargo.toml, Cargo.lock, Dockerfile, .dockerignore) while excluding documentation (docs/, *.md files). No changes to job steps or runtime logic.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/docker-and-install

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant