feat(generate): add provider default exclude patterns - #670
Open
iloveitaly wants to merge 7 commits into
Open
Conversation
Collaborator
Author
|
@coffee-cup this change is a little risky, but I think these sort of smart defaults make a lot of sense for users. |
- Configure default exclusion patterns for Node, Deno, and Python providers during build planning. - Remove obsolete node_modules warning logic now handled by default exclusions. Generated-by: aiautocommit
…exist - Add provider default exclude support to GenerateContext - Fall back to provider defaults and warn users when no `.dockerignore` or config excludes are provided - Prioritize user-defined `.dockerignore` and config excludes over provider defaults Generated-by: aiautocommit
Generated-by: aiautocommit
Generated-by: aiautocommit
Generated-by: aiautocommit
iloveitaly
force-pushed
the
build/default-dockerignore
branch
from
August 10, 2026 20:50
f166e74 to
84e767c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation
Projects without a
.dockerignoreor configured excludes can send unnecessary dependency and cache files into the build context, increasing build overhead.Description
Provider-specific defaults now supply sensible exclude patterns when users have not defined their own. Explicit
.dockerignoreand configuration excludes take precedence, while Node, Deno, and Python providers define their respective defaults.Breaking Changes
Projects without a
.dockerignoreor configured excludes will now omit.git, dependency, and local virtual-environment directories from the build context by default. Builds that intentionally rely on checked-innode_modules,venv, or.venvmay be affected; users should add a.dockerignoreor adjust their exclude configuration as needed.Test