fix: no source tracking after a dry-run @W-18067034@ #1372
Merged
Conversation
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
Contributor
|
QA: |
WillieRuemmele
force-pushed
the
wr/noSourceTrackingWithDryRun
branch
from
1138556 to
f380338
Compare
shetzel
approved these changes
Jun 17, 2025
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 does this PR do?
when doing a
deploy start --dry-run --source-dir force-appthere shouldn't be source-tracking used anywhererunning that command, and then a
sf project deploy startshould pick up everything as unchanged
currently, the dry-run is affecting source-tracking, and the secnod command wasn't deploying anything
fixes it so they're independent
What issues does this PR fix or reference?
@W-18067034@
forcedotcom/cli#3243