Skip to content
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

Update api used to get workspace path on source:deploy #738

Merged
merged 1 commit into from
Nov 9, 2018

Conversation

lcampos
Copy link
Contributor

@lcampos lcampos commented Nov 9, 2018

What does this PR do?

Updates the api used to set the workspace path when running source:deploy.

What issues does this PR fix or reference?

@W-5608272@, #737, #734

@codecov
Copy link

codecov bot commented Nov 9, 2018

Codecov Report

Merging #738 into develop will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #738   +/-   ##
========================================
  Coverage    74.16%   74.16%           
========================================
  Files          163      163           
  Lines         6615     6615           
  Branches      1037     1037           
========================================
  Hits          4906     4906           
  Misses        1440     1440           
  Partials       269      269
Impacted Files Coverage Δ
...cedx-vscode-core/src/commands/forceSourceDeploy.ts 42.5% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d946862...999c5a5. Read the comment docs.

@lcampos lcampos merged commit 227abf4 into develop Nov 9, 2018
@lcampos lcampos deleted the lcampos/fix-sourceDeploy-win branch November 9, 2018 21:51
@salesforce-cla
Copy link

salesforce-cla bot commented May 5, 2021

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Luis Campos <l***@s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, refresh the status of this Pull Request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants