fix(api): honor linked project root directory - #268
Open
swingo35 wants to merge 1 commit into
Open
Conversation
Hydralerne
marked this pull request as ready for review
July 29, 2026 22:06
Member
|
are we fine to merge ? |
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
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.
What changed
rootDirectorywhen resolving Compose drift from GitHubWhy
An adopted local Compose project can be linked to a GitHub repository whose deployment manifest lives in a subdirectory. Previously, the link kept
localPath, while drift reconciliation auto-detected the repository root and could import unrelated services. This makes the linked GitHub repository and configured root the actual deployment source.Validation
bun run --cwd apps/api test -- test/modules/deployments/prepare.service.test.tsbun run --cwd apps/api lintgit diff --check