From 66f1cb08a832fbbc941dffbb8e30a93d106b34d8 Mon Sep 17 00:00:00 2001 From: Kamil Kisiela Date: Tue, 7 Jan 2025 10:10:08 +0100 Subject: [PATCH] Mention Hive in the documentation of the diff command (#2837) --- website/src/pages/docs/commands/diff.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/website/src/pages/docs/commands/diff.mdx b/website/src/pages/docs/commands/diff.mdx index a77501883d..785a945388 100644 --- a/website/src/pages/docs/commands/diff.mdx +++ b/website/src/pages/docs/commands/diff.mdx @@ -13,6 +13,14 @@ Detect changes to your GraphQL Schema and prevent breaking your existing applica Inspector you get a list of breaking, potentially dangerous and safe changes on every Pull Request. Integrate it with GitHub, BitBucket, GitLab or any Continuous Integration. +> While GraphQL Inspector is effective for comparing two schema versions and identifying changes, +> for a more comprehensive and robust approach to schema management, consider using +> [GraphQL Hive](https://the-guild.dev/graphql/hive). GraphQL Hive offers a fully open-source schema +> registry for GraphQL APIs. It provides features such as version control and schema checks to +> detect breaking changes before they reach production, allowing you to evolve your API with +> confidence. . Additionally, GraphQL Hive offers insights into API usage and performance metrics, +> making it a more robust solution for managing and evolving your GraphQL schemas. + ![Application](/assets/img/github/app-action.jpg) ## You can choose between: