Refactor CircleCI config for testing workflow

[Dargon789]

Summary by Sourcery

Refactor the CircleCI configuration to run tests in a Forge-based Docker job and simplify the workflow naming.

CI:

• Replace the custom executor and job with a single test job using the ghcr.io/foundry-rs/foundry:latest Docker image.
• Add explicit steps for checking out the code, initializing git submodules, building with forge build, and running tests with forge test -vvv.
• Rename the workflow to main and update it to run only the new test job.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refactors the CircleCI pipeline to use a simple Foundry-based test job and workflow instead of a custom executor and placeholder job, adding concrete build and test steps.

File-Level Changes

Change	Details	Files
Replace custom executor-based job with a Docker job using the Foundry image and explicit build/test steps.	Remove the reusable custom Docker executor configuration that relied on Docker Hub credentials. Define a new test job that runs in the ghcr.io/foundry-rs/foundry:latest container. Add steps to checkout the code, initialize git submodules, run forge build, and run forge test -vvv.	.circleci/config.yml
Simplify and rename the workflow to run the new test job.	Remove the previous my-custom-workflow workflow and its job reference. Define a new main workflow that runs the test job.	.circleci/config.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Consider pinning the Foundry Docker image to a specific version or digest instead of latest to avoid unexpected breakages from upstream image changes.
• You can speed up repeated builds by adding CircleCI caching for the forge artifacts (e.g., cache steps keyed on foundry.toml and lib contents) instead of rebuilding everything from scratch on each run.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider pinning the Foundry Docker image to a specific version or digest instead of `latest` to avoid unexpected breakages from upstream image changes.
- You can speed up repeated builds by adding CircleCI caching for the `forge` artifacts (e.g., `cache` steps keyed on `foundry.toml` and `lib` contents) instead of rebuilding everything from scratch on each run.

## Individual Comments

### Comment 1
<location path=".circleci/config.yml" line_range="9-14" />
<code_context>
-      - run: |
-          # echo Hello, World!
-
+      - run:
+          name: Install submodules
+          command: git submodule update --init --recursive
+      - run:
+          name: Build
+          command: forge build
+      - run:
+          name: Test
</code_context>
<issue_to_address>
**suggestion (performance):** Add caching for build artifacts to speed up repeated `forge build`/`forge test` runs.

Since `forge build` / `forge test` currently run from scratch on every CI execution, consider using CircleCI workspaces or `save_cache` / `restore_cache` keyed on `foundry.toml` plus `lib`/`src` checksums to cache the `out` directory (and optionally the Foundry artifacts dir) to reduce build times while preserving correctness.

Suggested implementation:

```
    steps:
      - checkout
      - run:
          name: Install submodules
          command: git submodule update --init --recursive
      - restore_cache:
          keys:
            - v1-forge-out-{{ checksum "foundry.toml" }}-{{ checksum "lib" }}-{{ checksum "src" }}
            - v1-forge-out-
      - run:
          name: Build
          command: forge build
      - save_cache:
          key: v1-forge-out-{{ checksum "foundry.toml" }}-{{ checksum "lib" }}-{{ checksum "src" }}
          paths:
            - out
            - ~/.foundry
      - run:
          name: Test
          command: forge test -vvv

```

CircleCI's `checksum` function officially operates on files; if `lib` and `src` are directories in your repo, you may want to replace `{{ checksum "lib" }}` / `{{ checksum "src" }}` with checksums of specific files (e.g., a lockfile, or a generated checksum file for those directories) to conform strictly to CircleCI's capabilities.
</issue_to_address>

Fix all in Cursor

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request updates the CircleCI configuration to use the Foundry toolchain, replacing the previous custom executor with a test job that handles submodule initialization, building, and testing. Feedback suggests pinning the Docker image version to avoid non-deterministic builds and using the --depth 1 flag during submodule updates to optimize CI build times.