ci: add testnet explorer url

[fmorency]

Summary by CodeRabbit

• New Features
  • Introduced a new environment variable, NEXT_PUBLIC_TESTNET_EXPLORER_URL, to enhance configuration options during Docker image builds.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the Docker workflow configuration by adding a new environment variable, NEXT_PUBLIC_TESTNET_EXPLORER_URL, to the .env file during its creation. This variable is derived from vars.NEXT_PUBLIC_TESTNET_EXPLORER_URL. The overall job structure and other steps within the workflow remain unchanged, focusing solely on the addition of this new variable.

Changes

File	Change Summary
.github/workflows/docker.yml	Added NEXT_PUBLIC_TESTNET_EXPLORER_URL to .env file creation step.

Possibly related PRs

• ci: docker testnet #58: The main PR updates the .env file creation step in the Docker workflow, which is directly related to the new GitHub Actions workflow introduced in PR ci: docker testnet #58 that also involves creating a .env file for the Docker image build process.

Suggested labels

enhancement

Suggested reviewers

• jgryffindor
• chalabi2

Poem

🐇 In the world of code, we hop and play,
A new variable joins us today!
With NEXT_PUBLIC_TESTNET_EXPLORER_URL in sight,
Our Docker builds shine ever so bright!
So let’s cheer and dance, oh what a delight! 🎉

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.42%. Comparing base (54274d7) to head (7e677a4).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #93   +/-   ##
=======================================
  Coverage   59.42%   59.42%           
=======================================
  Files         146      146           
  Lines       14187    14187           
=======================================
  Hits         8430     8430           
  Misses       5757     5757           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.