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
Originally posted by Maxr1998 January 23, 2022
When running beet mbsync, the command should print the proposed changes, and then ask for approval, similarly to beet modify.
That's because changes on MusicBrainz may not always be expected or wanted.
Always running the command with -p first, checking the output, and running it again without the flag is tedious (and may even introduce race conditions if something gets edited in between, even if unlikely).
For the old behavior, a -y flag could be introduced, or a configuration file option.
The text was updated successfully, but these errors were encountered:
IMHO it's not necessary to change the current behavior. We could also just introduce a new --timid flag (similar to import --timid) and keep the current behavior as-is.
Discussed in #4247
Originally posted by Maxr1998 January 23, 2022
When running
beet mbsync
, the command should print the proposed changes, and then ask for approval, similarly tobeet modify
.That's because changes on MusicBrainz may not always be expected or wanted.
Always running the command with
-p
first, checking the output, and running it again without the flag is tedious (and may even introduce race conditions if something gets edited in between, even if unlikely).For the old behavior, a
-y
flag could be introduced, or a configuration file option.The text was updated successfully, but these errors were encountered: