-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beta Source plugin regression: Source tracking detects Document metadata is in conflict with server source version #1398
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Works on my machine...I think that's a bug in how we're handling windows paths (based on the visible differences in the output) Nice catch! |
This issue has been linked to a new work item: W-10678360 |
Just want to note that this same conflict is reported when you do a
|
Summary
While testing the force:source:beta:push command, I found that I received conflict errors for Document metadata on the second issuance of the command (there should've been no conflicts since the file was already pushed successfully and was not modified server side nor client side)
Steps To Reproduce:
Repository to reproduce:
https://github.com/patronmanager/beta-source-push-document-bug
The README in that repo has the steps but I'll repeat here:
Expected result
This is what happens with the GA plugin (no error; no files to push)
Actual result
This is what happens with the
beta
pluginSystem Information
The text was updated successfully, but these errors were encountered: