-
Notifications
You must be signed in to change notification settings - Fork 18
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
Sm/status-shows-ignores #258
Conversation
Authored via Leif
* test: one NUT for special types * test: remove tracking NUTs * ci: custom nut commands * test: fix folderTypes, cross-env for windows * test: cross-env for windows SEED_FILTER, nyc only top-level * ci: no sha; change nut order * test: deploy nuts in parallel * ci: disable async nuts * test: exclude async nuts * test: revert async-exclude * test: revert tsconfig, revert config.yml * test: exclude env for seeds
* fix: implementing destructive change deploy, 1 NUT * chore: add NUTs, fix UTs * chore: post-review board updates * chore: fix linting * chore: minor updates to flag logic, redo NUT query method * chore: remove unnecessary checks in NUTs * chore: bump SDR to 5, include deploy:destructive in NUTs
@@ -52,7 +52,7 @@ workflows: | |||
- linux | |||
- windows | |||
node_version: | |||
- latest | |||
# - latest |
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.
why the comment?
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.
node latest is v17 and there's an temporary issue with that
@@ -12,7 +12,7 @@ | |||
{ | |||
"command": "force:source:beta:status", | |||
"plugin": "@salesforce/plugin-source", | |||
"flags": ["all", "apiversion", "json", "local", "loglevel", "remote", "targetusername"] | |||
"flags": ["apiversion", "json", "local", "loglevel", "remote", "targetusername"] |
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.
Are we able to remove the 'all' flag without deprecation?
What does this PR do?
Draft because requires 2 PRs:
forcedotcom/source-tracking#40 which requires forcedotcom/source-deploy-retrieve#479
PR feedback from #209
other:
SourceTrackingResetCommand
->Reset
)state
property (fancy TS literal forstate
prop)--all
flag on status, make remote/local exclusive