Skip to content

Commit 6d9630d

Browse files
Fixing lint errors
1 parent 418ccd9 commit 6d9630d

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

website/pages/en/deploying/multiple-networks.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@
22
title: Deploying a Subgraph to Multiple Networks
33
---
44

5-
65
This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
76

87
## Deploying the subgraph to multiple networks
@@ -239,4 +238,4 @@ Graph Node exposes a GraphQL endpoint which you can query to check the status of
239238
}
240239
```
241240

242-
This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
241+
This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.

0 commit comments

Comments
 (0)