You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2023. It is now read-only.
When devs are working in parallel in the same dev space, when one dev applies a script to the space, other devs can gets an error, because the script is not in their local workspace yet.
Sorry to bother you again @deluan, to restate we are willing to contribute the code to add an option (like warn-if-missing-scripts or warn-missing or something) and catch any missing script error and output a warning instead if the option is given on the command line. What do you think?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When devs are working in parallel in the same dev space, when one dev applies a script to the space, other devs can gets an error, because the script is not in their local workspace yet.
There should be a way to make this error a warning instead, so it does not break any dev's workflow
The text was updated successfully, but these errors were encountered: