Deploy on save exclusions #5792
robert-strunk
started this conversation in
Ideas
Replies: 2 comments
-
I have this problem too. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I thought that |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
I have Deploy on Save enabled. When I am working on LWC unit tests, each save triggers a failing push/deploy. Its a bit distracting.
Describe the solution you'd like
There may already be some mechanism to prevent that from happening but I wasn't able to find anything. I think a solid solution would be to create a new setting that allows you to specify directories that should not be included in the deploy on save functionality (similar to how a .forceignore ignores directories/files on push/pull/status)
Describe alternatives you've considered
Disabling deploy on save. I've also looked for existing settings/mechanisms that may address this issue.
Beta Was this translation helpful? Give feedback.
All reactions