Skip to content

add deploy to DAO scripts#238

Merged
Joeysantoro merged 6 commits intomasterfrom
feat/deploy-in-dao-script
Oct 12, 2021
Merged

add deploy to DAO scripts#238
Joeysantoro merged 6 commits intomasterfrom
feat/deploy-in-dao-script

Conversation

@Joeysantoro
Copy link
Contributor

@Joeysantoro Joeysantoro commented Oct 12, 2021

Now FIP flows can write their deploy function only inside their proposals/dao script to stay focused on one file

README changes assume run is already removed from the dao scripts

xklob
xklob previously approved these changes Oct 12, 2021
Joey Santoro and others added 2 commits October 11, 2021 19:42
## Optional Step 4: Deploying and Updating Addresses
If your contract has an optional deployment step from above, you need to deploy your new contracts to mainnet before moving on to Step 5.

Run `DEPLOY_FILE=fip_x npm run deploy:fip`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add a note here that says if you need to deploy to mainnet, you run DEPLOY_FILE=fip_x npm run deploy:fip --network mainnet and note that this step is not necessary when running E2E tests.

@Joeysantoro Joeysantoro merged commit dbba7bf into master Oct 12, 2021
@Joeysantoro Joeysantoro deleted the feat/deploy-in-dao-script branch October 12, 2021 03:37
Then run `npm run test:e2e`

## Step 6: Propose on-chain
## Step 5: Propose on-chain
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need one more step before step 5 and that is simulating what happens with calldata you generated using npm run check-proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments