Please don't use the main OSM database for "test adding" objects. There is a dedicated development server for these purposes.

Also, please read and follow the import guidelines before uploading any external dataset:

osm.wiki/Import/Guidelines

Hi,
"prenotation = required" is not a common tag (and not an English word).
Do you need to make an appointment to enter? Then maybe opening_hours = "on appointment" would be appropriate.

If you just need to get a permit, the tag could be
foot:conditional = yes @ permit

Hi,
the access and turn lanes you added here are not used in other places and don't fit the usual tagging schemes.
Could you explain what you wanted to tag?

access:lanes:left = forward
access:lanes:right = forward
turn:lanes:left = forward
turn:lanes:right = forward

Welcome to OSM!
you used many tags here that are not in use in any other place. Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
This is necessary to make sure that every other user can understand the data.

Examples of these problematic tags are:
accessibility_pwd = true
facility_gps-latitude = -1.3105014
facility_gps-longitude = 36.8635287
facility_owner = private/individual
facility_pay = true
facility_use = car wash services

You can use these keys to specify the different companies and people involved:

brand
operator
owner

Please excuse my spelling mistake - it should be

gtfs:stop_id:FR-MAT

Hi,
you added the new tag "gtfs:stop_id:Malo Agglo Transports" here. In general keys should not contain any spaces.

If you look at the list of other gtfs tags you can see that the more usual scheme is slightly different:
https://taginfo.openstreetmap.org/keys/gtfs%3Astop_id#similar

The tag should contain a country code (to make clear where this tag is in use and to prevent duplicate tags across the world, followed by an abbreviated name or acronym.
So here I'd suggest to use

gtfs:stop_id:FR:MAT

Ja genau.
Hat OsmAnd da keine vorgegebenen Keys? Das würde mich wundern, da die Werte (lane, underground) ja korrekt sind.

Schau mal in die Tabellen auf der verlinkten Wiki-Seite
fire_hydrant:diameter=*
fire_hydrant:position=*
fire_hydrant:type=*

Hi,
you added the new tag "coco=yes" here - what does it mean?

Hi,
you used many tags here that are not in use in any other place. Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
This is necessary to make sure that every other user can understand the data.

Please have a look to the documented tags in the wiki and use only these - only well-defined tags can be understood by other mappers and can be shown on maps and in applications.

Welcome to OSM!
you used many tags here that are not in use in any other place. Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
This is necessary to make sure that every other user can understand the data.

Please have a look to the documented tags in the wiki and use only these - only well-defined tags can be understood by other mappers and can be shown on maps and in applications.

Hi,
could you explain what these tags mean? You added them to many buildings, but they are neither documented nor used in other places.

Cooling_center = yes
Cooling_center_bd = yes

Hallo,
bitte überprüfe deine Änderungen an Hydranten - diese deutschen Tags sind nicht korrekt:

Durchmesser = 150
Position = lane
Typ = underground

osm.wiki/DE:Tag:emergency=fire_hydrant

Please stop reverting the edits of other mappers.
You repeatedly added undocumented tags here which already have been fixed three times.

Hi,
could you point us to the mandatory import documentation?
All these ways have many foreign tags that shouldn't be in OSM.
Also, none of these ways is connected to any other highway, which makes the ways rather useless, because they are just loops that can't be reached from anywhere.

Hi,
please check this import - all the buildings have strange tags:

dont_tag_buildings = False
dont_tag_buildings2 = False

We're too late, it is already fixed:
way/1321559906

First, there are many people who don't want to publish their prices and menu on the internet for various reasons.
Second, there is a problem of copyright with respect to printed menus: Often the creator / designer of them has a copyright that doesn't allow further copies or reproductions of the work, like with any other printed material.

Third, if the owner wants to have his menu published, they likely put it on their web page. Then we can just add a link using website:menu=*

There is a general consensus that OSM is not a directory of prices of various amenities. See e.g. here in a recent question about hotel prices:

https://community.openstreetmap.org/t/complex-hotel-price-charge-or-charge-conditional/115275/1