Will it be possible to sf project deploy start to deploy without source tracking #2497
Replies: 3 comments 3 replies
-
If a scratch org, use And if you just want to override all the conflicts with your deploy, you can |
Beta Was this translation helpful? Give feedback.
-
But now there is another problem, If I won't provide the user flag then I will get the error that job was not found |
Beta Was this translation helpful? Give feedback.
-
Note that if you have an org you'd like to disable tracking for, you can do that with the newish https://github.com/forcedotcom/cli/blob/main/releasenotes/README.md#2197-nov-29-2023 |
Beta Was this translation helpful? Give feedback.
-
Hi All,
I was trying to migrate from the previous sfdx commands to the new sf command but I've faced some serious problems.
I cannot run the
sf project deploy start
on the organization that has source tracking enabled because of conflicts.
Of course, it is possible to run sf project deploy validate but this command does not have an --ignore-warning flag.
The command that is working correctly is
sf force:source:deploy
but this command already has a warning that will be deprecated.
I do not need to be worried about the conflict which I do not care about at that time as the code base that I'm trying to deploy is the one that I want to have in the sandbox.
I suspected that the command alignment would not change the overall behavior but now it is.
I would like to know your opinion on this and maybe someone from the creator could put some more light on this one.
Beta Was this translation helpful? Give feedback.
All reactions