ForceCLI's behavior with the force push -f command is inconsistent when provided with the path of these individual component files.

force push -f aura/comp/comp.cmp works, and pushes changes to the component markup only (any changes to the JavaScript files are not pushed).

However, force push -f aura/comp/compController.js or force push -f aura/comp/compHelper.js fails to deploy and emits the following message:

```
Successes - 1
comp: changed

Test Successes - 0

Failures - 2
Main markup cannot be empty. If you are trying to delete the Lightning definition bundle, directly delete the bundle instead.
Main markup cannot be empty. If you are trying to delete the Lightning definition bundle, directly delete the bundle instead.

Test Failures - 0
ERROR: Some components failed deployment
```

It would be very useful to be able to pass any component element filename to force push -f, particularly for delta-deployment workflows like git diff --name-only ... | force push -f -.

All three resource files are invalid ZIPs according to Windows Explorer and 7zip. (I do not have access to a Linux machine at work to validate these files). References within the static resource on Salesforce return 404 errors.

force fetch -t Flow used to fetch all active and inactive flow files. In Winter 19, Salesforce stopped appending a version # to the end of the Flow filename and the fetch command only retrieves the active version of each Flow.