Skip to content

Commit 80b8a89

Browse files
authored
Managing sub (#787)
* separating pages * redirects
1 parent ea09775 commit 80b8a89

File tree

52 files changed

+584
-35
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

52 files changed

+584
-35
lines changed

nginx.conf

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -90,11 +90,8 @@ http {
9090
rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$ $scheme://$http_host/docs/$1/quick-start/ permanent;
9191
rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/assemblyscript-api/$ $scheme://$http_host/docs/$1/developing/graph-ts/api/ permanent;
9292
rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/assemblyscript-api/$ $scheme://$http_host/docs/$1/developing/graph-ts/api/ permanent;
93-
rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/deprecating-a-subgraph/$ $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/ permanent;
94-
rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transferring-subgraph-ownership/$ $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/ permanent;
9593
rewrite ^/docs/en/substreams/(?!index\.).+$ https://substreams.streamingfast.io permanent;
9694
rewrite ^/docs/en/firehose/(?!index\.).+$ https://firehose.streamingfast.io permanent;
97-
9895
# Temporary redirects (302)
9996
rewrite ^/docs/en/querying/graph-client/$ $scheme://$http_host/docs/en/querying/graph-client/README/ redirect;
10097
rewrite ^/docs/en/developing/graph-ts/$ $scheme://$http_host/docs/en/developing/graph-ts/README/ redirect;
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Deprecate a Subgraph
3+
---
4+
5+
## Deprecating a Subgraph
6+
7+
Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
8+
9+
### Step-by-Step
10+
11+
To deprecate your subgraph, do the following:
12+
13+
1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
14+
2. Call `deprecateSubgraph` with your `SubgraphID` as your argument.
15+
3. Your subgraph will no longer appear in searches on Graph Explorer.
16+
17+
**Please note the following:**
18+
19+
- The owner's wallet should call the `deprecateSubgraph` function.
20+
- Curators will not be able to signal on the subgraph anymore.
21+
- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
22+
- Deprecated subgraphs will show an error message.
23+
24+
> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/yo/managing/transfer-and-deprecate-a-subgraph.mdx renamed to website/pages/ar/managing/transfer-a-subgraph.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Transfer and Deprecate a Subgraph
2+
title: Transfer a Subgraph
33
---
44

55
## Transferring ownership of a subgraph
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Deprecate a Subgraph
3+
---
4+
5+
## Deprecating a Subgraph
6+
7+
Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
8+
9+
### Step-by-Step
10+
11+
To deprecate your subgraph, do the following:
12+
13+
1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
14+
2. Call `deprecateSubgraph` with your `SubgraphID` as your argument.
15+
3. Your subgraph will no longer appear in searches on Graph Explorer.
16+
17+
**Please note the following:**
18+
19+
- The owner's wallet should call the `deprecateSubgraph` function.
20+
- Curators will not be able to signal on the subgraph anymore.
21+
- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
22+
- Deprecated subgraphs will show an error message.
23+
24+
> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.
File renamed without changes.
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Deprecate a Subgraph
3+
---
4+
5+
## Deprecating a Subgraph
6+
7+
Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
8+
9+
### Step-by-Step
10+
11+
To deprecate your subgraph, do the following:
12+
13+
1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
14+
2. Call `deprecateSubgraph` with your `SubgraphID` as your argument.
15+
3. Your subgraph will no longer appear in searches on Graph Explorer.
16+
17+
**Please note the following:**
18+
19+
- The owner's wallet should call the `deprecateSubgraph` function.
20+
- Curators will not be able to signal on the subgraph anymore.
21+
- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
22+
- Deprecated subgraphs will show an error message.
23+
24+
> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.
File renamed without changes.

website/pages/en/developing/developer-faqs.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ If only one entity is created during the event and if there's nothing better ava
8080

8181
### 15. Can I delete my subgraph?
8282

83-
It is not possible to delete subgraphs once they are created. However, you can [transfer and deprecate your subgraph](/managing/transfer-and-deprecate-a-subgraph/).
83+
It is not possible to delete subgraphs once they are created. However, you can [transfer](/managing/transfer-a-subgraph/) and [deprecate](/managing/deprecate-a-subgraph/) your subgraph.
8484

8585
## Network Related
8686

website/pages/en/managing/_meta.js

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
11
export default {
2-
'transfer-and-deprecate-a-subgraph': '',
2+
'transfer-a-subgraph': '',
3+
'deprecate-a-subgraph': '',
34
}
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
title: Deprecate a Subgraph
3+
---
4+
5+
Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
6+
7+
## Step-by-Step
8+
9+
To deprecate your subgraph, do the following:
10+
11+
1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
12+
2. Call `deprecateSubgraph` with your `SubgraphID` as your argument.
13+
3. Your subgraph will no longer appear in searches on Graph Explorer.
14+
15+
## Reminders
16+
17+
- The owner's wallet should call the `deprecateSubgraph` function.
18+
- Curators will not be able to signal on the subgraph anymore.
19+
- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
20+
- Deprecated subgraphs will show an error message.
21+
22+
> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

0 commit comments

Comments
 (0)