-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mimic MBS edit note validation and warnings #712
Comments
You have forgot to write an edit note for the edit reviewers and for history. It's the same if you don't use the userscript. Merging entities is a destructive edit. I will change my scripts (MERGE HELPOR 2 and MASS MERGE RECORDINGS) to mimic MBS, using the same error messages and styling. |
Ah sorry, I see that you did write an edit note:
My scripts are validating edit notes and they think this one is not enough. 🤣 Didn't my script explain this?
Did you see this warning? |
Notes to myself:
|
Maybe you could lower the threshold for release groups only. Two release groups with the same name are very rarely correct. In the last few weeks/month I see a lot of new users using some scripts to scan their music collection and adding release groups even if there is already one. In my example the band 10cc had their last release 27 years ago, yet some newbie thought he should add each album with a new release group. https://musicbrainz.org/artist/f37c537b-3557-4031-bfd6-ab63ced32854 Maybe Musicbrainz should make it much harder for new users to create release groups. |
MBS forbids ".." and "a" I additionally forbid ".a." and " a "
Align on valid edit note conditions and text Stop using (cu)cumbersome alerts
When merging release groups, I get the warning about the destructive edit and after clicking OK it goes back and the edit note field is highlighted in red. What am I doing wrong?
Firefox 105.0.3
Greasemonkey 4.11
Kubuntu 22.04
The text was updated successfully, but these errors were encountered: