Our great sponsors
-
graphql-tools
:wrench: Utility library for GraphQL to build, stitch and mock GraphQL schemas in the SDL-first approach
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
graphql-inspector
🕵️♀️ Validate schema, get schema change notifications, validate operations, find breaking changes, look for similar types, schema coverage
-
apollo-angular
A fully-featured, production ready caching GraphQL client for Angular and every GraphQL server 🎁
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Doing this was pretty simple. You can find the repo here which is used as the master repository to push all the labels downstream and we still retain the repo specific labels in their own repository (like this)
GraphQL Tools
GraphQL Inspector
Apollo Angular
This led us to the creation of the contributor workflow guide to help us standardize the workflow, guide beginners who would like to contribute and also act as a guide for other open source projects who are looking at a similar standardization approach (What we have is an initial iteration of the guide and there is definitely a lot of room for improvement. If you have any suggestions, do let us know - we are all ears 🙂)
Doing this was pretty simple. You can find the repo here which is used as the master repository to push all the labels downstream and we still retain the repo specific labels in their own repository (like this)
This is when we strongly felt the need to sync/orchestrate labels across all the repositories while also respecting the differences between the projects (one size may not fit all). This led us to a proof of concept with different label syncing tools and after quite a bit of analysis, we landed on Label Syncer to manage both master and repository level declarative labels (If someone from Github is reading this, maybe this should be an inbuilt feature 😇)