[Github-actions] Add dev endpoint to deployment action
#321
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0xAurelius
approved these changes
Nov 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE: This is currently blocked as there issues creating a new subgraph in the studio. Most likely because of the multisig; reached out to graph support
Stagingwill need to be a clone of main for the new subgraph versioning process.The current
stagingwill becomedev. This PR updates the deploy action to deploy any subgraphs pushed to the dev branch to the dev endpoint.Unlike
stagingandmain, there are not differentdevendpoints for each individual subgraph. Instead subgraphs will be named - on thedevendpoint. The Graph auto-archives after three deployments but we can easily unarchive via the graph ui.We are not deploying to Alchemy as this would inflate the entity count beyond the billing limitations.