chore: move from dev:watch to watch
#6888
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: John Molakvoæ <skjnldsv@users.noreply.github.com>
ShGKme
approved these changes
May 7, 2025
susnux
approved these changes
May 7, 2025
Contributor
susnux
left a comment
susnux
left a comment
There was a problem hiding this comment.
I do not care, I thought dev:watch was the standard like having dev and dev:watch (similar test and test:coverage).
Should be documented somewhere.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So, we use
watcheverywhere, literally for over 7 years.I see some repos that are slowly usig this new
dev:watchsyntax. Can we please stick to the one we used for years ? 🙈nextcloud-vue/package.json
Line 17 in f27d675