Skip to content

fix: deduplicate deploy inputs when using --build-cmd#381

Merged
coffee-cup merged 2 commits intomainfrom
jr/fix-duplicate-deploy-inputs
Dec 1, 2025
Merged

fix: deduplicate deploy inputs when using --build-cmd#381
coffee-cup merged 2 commits intomainfrom
jr/fix-duplicate-deploy-inputs

Conversation

@coffee-cup
Copy link
Contributor

When --build-cmd is passed, config step processing was adding a default deploy output {"include": ["."]} even when the provider already added one. This caused hasSignificantOverlap to return true, forcing llb.Copy fallback instead of llb.Merge.

  • Add HasIncludeForStep helper to check if a path is already covered by existing deploy inputs
  • Skip adding duplicate deploy outputs when the path is already included

When --build-cmd is passed, config step processing was adding a default
deploy output {"include": ["."]} even when the provider already added
one. This caused hasSignificantOverlap to return true, forcing llb.Copy
fallback instead of llb.Merge.

Add HasIncludeForStep helper to check if a path is already covered by
existing deploy inputs before adding duplicates.
@coffee-cup coffee-cup force-pushed the jr/fix-duplicate-deploy-inputs branch from 6a7fdb4 to a36d81e Compare November 29, 2025 03:10
@coffee-cup coffee-cup merged commit 8afcba3 into main Dec 1, 2025
97 checks passed
@coffee-cup coffee-cup deleted the jr/fix-duplicate-deploy-inputs branch December 1, 2025 19:20
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