Skip to content

contracts-bedrock: add l1 deploy tag#5312

Merged
tynes merged 1 commit intodevelopfrom
feat/l1-deploy-tag
Mar 31, 2023
Merged

contracts-bedrock: add l1 deploy tag#5312
tynes merged 1 commit intodevelopfrom
feat/l1-deploy-tag

Conversation

@tynes
Copy link
Contributor

@tynes tynes commented Mar 31, 2023

Description

Prepares for adding in L2 deployment scripts by adding a l1 tag to the deploy scripts that should run on L1. Also add the tag flag to the deployment that happens in CI. The L2 contract deployments will be added in another commit. It is not a problem if the L2 contracts are deployed to L1 in a testing environment but using tags to save time and gas should be done. Also lints a few lines of code where awaits are nested, nested awaits are difficult to read.

@tynes tynes requested review from a team as code owners March 31, 2023 08:09
@tynes tynes requested review from ajsutton and maurelian March 31, 2023 08:09
@changeset-bot
Copy link

changeset-bot bot commented Mar 31, 2023

⚠️ No Changeset found

Latest commit: 0236d9e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify
Copy link

netlify bot commented Mar 31, 2023

Deploy Preview for opstack-docs canceled.

Name Link
🔨 Latest commit 0236d9e
🔍 Latest deploy log https://app.netlify.com/sites/opstack-docs/deploys/64269c85edb16d0008108e84

Prepares for adding in L2 deployment scripts by adding
a `l1` tag to the deploy scripts that should run on L1.
Also add the tag flag to the deployment that happens
in CI. The L2 contract deployments will be added in
another commit. It is not a problem if the L2 contracts
are deployed to L1 in a testing environment but using
tags to save time and gas should be done. Also lints
a few lines of code where awaits are nested, nested
awaits are difficult to read.
@tynes tynes force-pushed the feat/l1-deploy-tag branch from 8b27f29 to 0236d9e Compare March 31, 2023 08:40
Copy link
Contributor

@maurelian maurelian left a comment

Choose a reason for hiding this comment

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

This is good for me, though I am slightly confused about why it is necessary. All of these scripts are specific to L1.

@tynes
Copy link
Contributor Author

tynes commented Mar 31, 2023

L2 deployments coming soon

@tynes tynes merged commit b00425e into develop Mar 31, 2023
@tynes tynes deleted the feat/l1-deploy-tag branch March 31, 2023 13:07
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