ci: skip container builds for documentation changes #148
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Skip expensive container builds when only documentation files are changed, reducing CI time and GitHub Actions usage.
Problem
Currently, every change triggers a full container build (~5-10 minutes), even when only editing markdown documentation files. This wastes CI resources and delays doc-only PR merges.
Solution
Add
paths-ignorefilters to the build workflow to skip builds when only these files change:*.md- All markdown files (README.md, AGENTS.md, etc.)LICENSE- License file.gitignore- Git configurationWhat Still Triggers Builds ✓
Containerfilechangessystem_files/**changesJustfileor**.justchangesbluefin-brandingsubmodule updatesworkflow_dispatch)Benefits
validate-just.ymlTesting
This PR itself only changes the workflow file, so it will trigger a build (as expected). Future documentation PRs will skip the build.
To verify:
References
validate-just.ymlandvalidate-brewfiles.yaml