fix: build workflow and generate addresses

fadeev commented 3 months ago

added a build workflow to ensure that the code builds before it gets merged
updated Amoy contract addresses

Summary by CodeRabbit

New Features
- Added new address entries for amoy_testnet and zeta_testnet chains, enhancing support for various categories like messaging, omnichain, and connector.
- Addresses support types such as tss, erc20Custody, pauser, tssUpdater, and zetaToken, increasing functionality and integration options.

coderabbitai[bot] commented 3 months ago

[!IMPORTANT]

Review skipped

Review was skipped due to path filters

Files ignored due to path filters (3)
* `package.json` is excluded by none and included by none * `tasks/addresses.ts` is excluded by none and included by none * `yarn.lock` is excluded by `!**/yarn.lock`, `!**/*.lock` and included by none

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent updates to data/addresses.testnet.json introduce new entries for multiple addresses on the amoy_testnet and zeta_testnet chains. These entries cover categories such as messaging, omnichain, and connector, specifying various types like tss, erc20Custody, and zetaToken. Each new entry includes details like address, chain ID, chain name, and relevant specifics.

Changes

File	Change Summary
`data/addresses.testnet.json`	Addition of new address entries across `omnichain`, `messaging`, and `connector` categories for `amoy_testnet` and `zeta_testnet`.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Database

    User->>Database: Request address for `MATIC.AMOY`
    Database-->>User: Return address `0x777915D031d1e8144c90D025C594b3b8Bf07a08d`

    User->>Database: Request connector address for `amoy_testnet`
    Database-->>User: Return address `0x60E6b70bC2761f878Ff992276612F67FbABC1761`

    User->>Database: Request address for `erc20Custody` on `amoy_testnet`
    Database-->>User: Return address `0xFDE448af6140a8702A1165c44A0895ebE24b0C02`

    User->>Database: Request address for `pauser` on `amoy_testnet`
    Database-->>User: Return address `0x55122f7590164Ac222504436943FAB17B62F5d7d`

Poem

In the realm of chains so vast,
New addresses added fast!
From amoy_testnet to Zeta's might,
Omnichain, messaging in sight.
A dance of tss and zetaToken true,
In JSON fields, the changes flew! 🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

codecov-commenter commented 3 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 50.06%. Comparing base (e33cd1f) to head (7c81340).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #203 +/- ## ======================================= Coverage 50.06% 50.06% ======================================= Files 22 22 Lines 795 795 Branches 171 205 +34 ======================================= Hits 398 398 Misses 397 397 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

zeta-chain / protocol-contracts