Delete .circleci directory

[Dargon789]

Summary by Sourcery

CI:

• Delete the .circleci/config.yml file to fully remove CircleCI workflow configuration.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
legion	Ready	Preview, Comment	Apr 11, 2026 1:49pm

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Removes the CircleCI configuration by deleting the entire .circleci/config.yml file, effectively disabling CircleCI pipelines for this repository.

File-Level Changes

Change	Details	Files
Remove CircleCI configuration from the repository.	Delete the .circleci/config.yml file that defined the CircleCI pipeline Stop running CircleCI-based workflows as part of this repo’s CI setup	.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.

[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]

Hey - I've reviewed your changes and they look great!

---

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 removes the CircleCI configuration file, which disables automated testing for the repository. The review feedback highlights that removing CI without a functional alternative or migration plan poses a risk to code quality and suggests either providing a new configuration or updating the current one to execute the project's tests.

I am having trouble creating individual review comments. Click here to see my feedback.

.circleci/config.yml (1-31)

Removing the CI configuration without providing a functional alternative leaves the repository without automated testing. For a smart contract project of this nature, maintaining a CI pipeline is essential for ensuring code quality and preventing regressions. If the intention is to migrate to another provider like GitHub Actions, it is recommended to include the new configuration in this pull request to avoid a gap in CI coverage. Otherwise, consider updating this configuration to execute the project's tests (e.g., forge test) instead of removing it entirely.

[Dargon789]

@Mergifyio refresh

[Dargon789]

@Mergifyio refresh

[mergify]

refresh

☑️ Command refresh ignored because it is already running from a previous command.

[mergify]

refresh

✅ Pull request refreshed