From 3a0c4ad4dbf28d4461f7b649e287f8ec7173e6ac Mon Sep 17 00:00:00 2001 From: Zach Pomerantz Date: Mon, 17 Jul 2023 10:33:50 -0700 Subject: [PATCH] fix: do not cache gql across CI (#6963) --- .github/actions/setup/action.yml | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/.github/actions/setup/action.yml b/.github/actions/setup/action.yml index 2672bd212e..107c3e3c27 100644 --- a/.github/actions/setup/action.yml +++ b/.github/actions/setup/action.yml @@ -40,16 +40,11 @@ runs: run: yarn contracts shell: bash - # GraphQL is generated from schema. The schema is always fetched, but if unchanged, graphql does not need to be re-generated. - - run: yarn graphql:fetch - shell: bash - - uses: actions/cache@v3 - id: graphql-cache - with: - path: src/graphql/**/__generated__ - key: ${{ runner.os }}-graphql-${{ hashFiles('src/graphql/**/schema.graphql') }} - - if: steps.graphql-cache.outputs.cache-hit != 'true' - run: yarn graphql:generate + # GraphQL is generated from schema and client-side graphql queries. The schema is always fetched and changes to + # client-side queries are hard to detect, so it is always re-generated. + # TODO(WEB-2498): Cache based on both fetched schema and client-side graphql queries. + # This will require some processing: cp all literal graphql tags into a separate file and hash it? + - run: yarn graphql shell: bash # Messages are extracted from source.