From e286ba616f42ec4e219eaa31cef2518c24503749 Mon Sep 17 00:00:00 2001 From: Jacob Thomason Date: Sun, 8 Oct 2023 18:33:55 -0400 Subject: [PATCH] Added CI badge --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 6be6f8b..b468137 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,7 @@ [![NPM Version](http://img.shields.io/npm/v/zapier-graphql.svg?style=flat)](https://www.npmjs.org/package/zapier-graphql) [![NPM Downloads](https://img.shields.io/npm/dm/zapier-graphql.svg?style=flat)](https://npmcharts.com/compare/zapier-graphql?minimal=true) +![CI](https://github.com/rentpost/zapier-graphql/actions/workflows/node.js.yml/badge.svg) Zapier Platform CLI is primarily designed for REST APIs. That does present some organizational questions when it comes to designing a Zapier CLI app. Further, REST APIs are huge question marks, in general. Whereas, GraphQL APIs all have an accessible typed schema. This CLI app is designed to make use of a GraphQL API's schema for