-
Notifications
You must be signed in to change notification settings - Fork 393
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
feat: Expose Deploy* and Retrieve* Commands for Scratch Orgs #4809
feat: Expose Deploy* and Retrieve* Commands for Scratch Orgs #4809
Conversation
Thanks for the contribution! Unfortunately we can't verify the commit author(s): Kenneth Lewis <k***@k***.i***.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, sign the Salesforce Inc. Contributor License Agreement and this Pull Request will be revalidated. |
3e75bbf
to
198e6d1
Compare
198e6d1
to
83ed0fe
Compare
83ed0fe
to
d74b429
Compare
…ken/W-11309172--deploy-retrieve-scratch-orgs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QA:
All the "new" deploy/retrieve commands appear and work in their given context
- ✅ Individual files
- ✅ Multi-selected files
- ✅ Entire directories
- ✅ Entire Project - Starting with Deploy was weird to fix up source tracking... Better to start w/ a scratch org using the Push command, and then using deploy iteratively.
- ✅ Command Palette
- ✅ Right-click menu in file
- ✅ Manifest file - as long as the version is correct :)
Source tracking is fixed up
- ✅ Local/remote changes for deploy -> view changes shows changes/doesn't show changes
Save on push/deploy
-❓ uses push by default. Do we want that? -> ✅ yes; will be fixed up by custom setting later!
Push/Pull
- ✅ Still available, still work!
Conflicts view
- ✅ Looks good
…tcom#4809) * feat: fixup source-tracking in deploy flow * chore: pkg lock * feat: squash merge of depl retr for scratch orgs branch * feat: now that stl ignores conflicts, no suppress * test: update tests to reflect last change * chore: fixup pkg json
What does this PR do?
What issues does this PR fix or reference?
@W-11309172@
Functionality Before
Functionality After