No worries, I just keep an eye on osmcha for changesets with my editor in case of any issues

En fait, il y aurait trois lignes à modifier, car si le name change, alors le name:br change sûrement aussi. Cela permet de mettre cela en évidence.
Le problème avec default_language, c'est qu'il ne semble pas du tout être utilisé par les consommateurs de données.

It looks like something went wrong for an empty changeset to be created. Maybe you can let me know what you were doing so I can see if there's something that needs fixing?
And also how you managed to group over 10000 changes into one changeset

Salut, j'ai dupliqué name en name:fr parce que c'est ce qui est conseillé sur le wiki pour les noms multilingues. J'ai jugé que ceux-ci n'étaient pas ambigus, donc qu'ils pouvaient facilement être faits tous en même temps.

Hi, for Greenfield Academy, can I check why you said that operator:wikidata=Q122616508 was incorrect?

Because that is the wikidata item for Advance Learning Partnership, which is the multi academy trust that the school is officially part of (https://www.get-information-schools.service.gov.uk/Establishments/Establishment/Details/149962)

way/404380284/history

Hi, thanks for updating these. Can you double check the phone number for Rancho Grande, it looks too long.
node/11806415065

I see, I haven't used OSMAnd much, so wasn't aware. A semicolon is definitely inappropriate however.
Osmose is clearly wrong in this case, either x or ext. Are commonly used to denote extensions.

Hi, thanks for updating these. Just a note, a semicolon isn't really the best way to show an extension, since semicolons are mainly used to separate multiple values. I've switched it to an x on node/12730205724

Thanks

Hi, thanks for adding the cafe. Can you double check the phone number though, it does not seem to be valid.
node/13793810348

This has been reverted in changeset/180779034

This has been reverted in changeset/180779034

I have reverted this vandalism in changeset/180778763

Ah apologies, I slipped up there. I've removed the incorrect number in the meantime

Thank you for noticing this and pointing it out, I had seen this error in a couple of other places and thought I had fixed all occurrences, apparently I missed this one.

Fixed in changeset/180586286

Hi, thanks for adding detail here, but you seem to have added several duplicate phone numbers that were already mapped using the contact: scheme
e.g. node/10553314712
way/266493096
etc.
Try to check for this, because there could be other places where conflicting data is added

Thank you for the feedback.

I feel like this sort of topic has been discussed many times before, of whether to have many individual changesets or fewer but limited in scope. My conclusion is that there are various suitable tools to analyse history which allow filtering by where edits are being made, by user and more and so having fewer changesets makes analysis of these bot edits easier.

The plan to have a maximum of one changeset per state per day was in the discussed proposal and no objections to that aspect were raised at the time. If you think there is something to add or a discussion to be had then please comment on the proposal thread or create a new topic in the forum.

I don't quite know what you mean there.

This edit only changed the phone value of node/3442248118 and did not change any other tags nor revert the phone tag to its previous value.

https://osmlab.github.io/osm-deep-history/#/node/3442248118

Hi, thanks for updating these.
Should these two identical schools be merged into one object? From aerial imagery they appear to be separate, but perhaps your local knowledge can assist here?
way/1296800407
way/1296800406

PS, I removed the building tag from them as the whole site is not a building

I'm not quite sure which of the nodes edited here you are talking about, but it wasn't the bot that made it look like a regular business, but rather the original edit would have done that.