From 4f776100e39bd9e8bff23aea6b84cec17e7e4097 Mon Sep 17 00:00:00 2001 From: Paul Razvan Berg Date: Mon, 16 Sep 2024 13:35:51 +0300 Subject: [PATCH] feat: instructions for listing deployments --- docs/contracts/v2/guides/10-custom-deployments.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/contracts/v2/guides/10-custom-deployments.mdx b/docs/contracts/v2/guides/10-custom-deployments.mdx index 3191bf06..e2b36196 100644 --- a/docs/contracts/v2/guides/10-custom-deployments.mdx +++ b/docs/contracts/v2/guides/10-custom-deployments.mdx @@ -176,3 +176,14 @@ forge script script/DeployPeriphery.s.sol \ If you are using a mnemonic or a hardware device for your deployer address, refer to `forge-script` page from the [Foundry Book](https://book.getfoundry.sh/reference/forge/forge-script#forge-script) for different wallet options. + +### Steps for listing the deployments + +Once the contracts are deployed, the final step is to list the deployment addresses and artifacts in the Sablier docs: + +1. List the deployment addresses by opening a PR in the + [docs repo](https://github.com/sablier-labs/docs/blob/main/docs/contracts/v2/02-deployments.md) +2. List the deployment artifacts by opening a PR in the + [deployments repo](https://github.com/sablier-labs/v2-deployments) + - Copy the generated artifact files (ABIs) from the `artifacts` directory. + - Copy the latest broadcast file from the `broadcast` directory.