chore: update ADOPTERS.md from global .github repo

Signed-off-by: microcks-bot <info@microcks.io>

Author: microcks-bot

ADOPTERS.md

@@ -49,6 +49,7 @@ This document also lists the organizations using Microcks based on public inform
 | [AsyncAPI Generator](https://github.com/asyncapi/generator) | [Lukasz Gornicki](https://www.linkedin.com/in/lukasz-gornicki-a621914/) | `Another project` | AsyncAPI Generator is a tool that, among other things, is responsible for providing functionality to generate clients/SDKs. Thanks to Microcks, we were able to provide acceptance testing infrastructure that allows us to test, on a pull request level, if generated clients actually work. Microcks provides mocks, and we communicate with them through generated clients. Some more details you can find [in this directory in the generator repo](https://github.com/asyncapi/generator/tree/master/packages/templates/clients/websocket/test), but this location is a subject for change as we want to start using Microcks not only for Websocket but now also for Kafka. |
 | [TransferGo](https://www.transfergo.com/) | [Zbigniew Malcherczyk](https://www.linkedin.com/in/zbigniew-malcherczyk/) | `end user` | TransferGo, founded in 2012, serves over 8 million customers across 160+ countries by providing fast and affordable international money transfers. Microcks has empowered our teams with AsyncAPI and OpenAPI server mocks, as well as a robust infrastructure for contract testing. |
 | [UEAT](https://ueat.io/) | [Olivier Beaudet](https://github.com/obeaudet-ueat) | `end user` | UEAT is a complete solutions for restaurant revenue growth. Online Ordering, Self-Ordering Kiosks, Hub Management, Table Ordering, POS Integration and more. Microcks has empowered our teams with OpenAPI server mocks. Allowing to mock third party integration, testing locally or via CI/CD. |
+| [GetYourGuide](https://www.getyourguide.com/) | [Lukasz Luszczynski](https://github.com/lukaszgyg) | `end user` | We use Microcks to mock OpenAPI-defined dependencies for local development and integration testing, enabling parallel, contract-based development across services. |
 |[XM](https://www.xm.com/) | [Stelios Gkiokas](https://github.com/sgkiokas) | `end user` | Microcks streamlines microservice development and testing by dynamically generating mocks from OpenAPI specs, gRPC contracts, and GraphQL schemas. Using Testcontainers, it replaces WireMock, gRPC Mock by Fadelis, and HttpGraphQlTester, while Kubernetes Operators allow teams to manage their own instances. This approach also enables realistic simulation of Payment Service Providers and provides a unified platform for developers, SETs, and QAs to collaborate effectively.|
 | [Amadeus](https://amadeus.com) | [Romain Quinio](https://www.linkedin.com/in/rquinio) [Kevin Viet](https://www.linkedin.com/in/vietk) [Basappa Vittalappa Dapalapur](https://www.linkedin.com/in/basu-dapalapur/) | `End-User` | We use Microcks to shift-left our mocking and contract-testing approach. For example, see how we use Microcks for mocking [OIDC](https://hub.microcks.io/package/openid.net/api/oidc.1.0) by checking out the slide deck from one of our talks on the subject! 👉 [Riviera DEV 2025](https://www.slideshare.net/slideshow/how-to-secure-your-apis-without-compromising-the-developer-experience-pdf/281499574).|
 | [Kiabi](https://kiabi.com) | [Emmanuel Peru](https://github.com/emmanuelperu) [Baptiste Desmasures](https://www.linkedin.com/in/baptiste-desmasures) | `end user` | We use **Microcks** to mock REST and Graphql API contracts, enable reliable testing, and streamline development workflows. It helps some of our teams ensure consistency, validate integrations early, and improve collaboration across different services. By simulating APIs, Microcks reduces friction in development and increases confidence in production deployments.|