Create CNAME

[Dargon789]

a317ddb

Summary by Sourcery

Limit CI tests to exclude UpgradeTests and add a CNAME file at the repository root.

CI:

• Update CI workflow to run Forge tests excluding the UpgradeTests contract.

Deployment:

• Add a root CNAME file, likely for custom domain configuration.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
legion	Canceled		Dec 21, 2025 2:23pm

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts the CI test command to exclude UpgradeTests and adds a CNAME file for GitHub Pages/custom domain configuration.

Sequence diagram for updated CI test execution excluding UpgradeTests

sequenceDiagram
    actor Developer
    participant GitHub
    participant GitHubActions
    participant CI_job
    participant Forge
    participant TestSuite
    participant UpgradeTests

    Developer->>GitHub: push_changes_or_open_PR
    GitHub-->>GitHubActions: trigger_ci_workflow
    GitHubActions->>CI_job: start_ci_yaml_job

    CI_job->>Forge: run forge_test_no_match_contract_UpgradeTests
    Forge->>TestSuite: collect_matching_tests
    TestSuite-->>Forge: return_tests_excluding_UpgradeTests
    Forge-->>CI_job: execute_tests_results

    CI_job-->>GitHubActions: report_ci_status
    GitHubActions-->>GitHub: update_commit_or_PR_status
    GitHub-->>Developer: show_ci_status_and_logs

Loading

File-Level Changes

Change	Details	Files
Modify CI workflow test step to run a narrower set of Forge tests.	Replace generic forge test --rerun -vvvvv invocation with forge test --no-match-contract UpgradeTests to skip UpgradeTests in CI Remove verbose and rerun flags from the Forge test command, relying on default behavior instead	.github/workflows/ci.yaml
Add CNAME file for GitHub Pages/custom domain configuration.	Create a new CNAME file at the repository root for DNS/custom domain setup (contents not visible in diff)	CNAME

---

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	Scanner	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.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new CNAME file to the repository. This file is crucial for enabling custom domain mapping, specifically pointing to a Vercel deployment. The change facilitates the use of a more user-friendly domain for the associated web application.

Highlights

• CNAME File Creation: A new CNAME file has been added to the repository, which is essential for configuring custom domains for web deployments.
• Custom Domain Configuration: The CNAME file specifies 'legion-rouge.vercel.app', indicating an intent to map a custom domain to a Vercel-hosted application.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/ci.yaml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a CNAME file, likely for configuring a custom domain with a service like Vercel. The change is straightforward. I have one suggestion to add a trailing newline to the file, which is a standard convention for text files and improves compatibility with various tools.

[sourcery-ai]

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

• The CI change from forge test --rerun -vvvvv to forge test --no-match-contract UpgradeTests will completely skip UpgradeTests; if that’s only meant as a temporary workaround, consider making it conditional (e.g., via an input or env flag) so upgrade coverage isn’t silently lost long term.
• The new CNAME file is added but appears empty in the diff; confirm that the expected custom domain value (e.g., example.com) is actually committed so GitHub Pages picks it up correctly.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The CI change from `forge test --rerun -vvvvv` to `forge test --no-match-contract UpgradeTests` will completely skip `UpgradeTests`; if that’s only meant as a temporary workaround, consider making it conditional (e.g., via an input or env flag) so upgrade coverage isn’t silently lost long term.
- The new `CNAME` file is added but appears empty in the diff; confirm that the expected custom domain value (e.g., `example.com`) is actually committed so GitHub Pages picks it up correctly.

## Individual Comments

### Comment 1
<location> `.github/workflows/ci.yaml:36` </location>
<code_context>
           UPGRADE_TEST_OLD_VERSION: ${{ secrets.UPGRADE_TEST_OLD_VERSION }}
         run: |
-          forge test --rerun -vvvvv
+          forge test --no-match-contract UpgradeTests

       - name: Format contracts and generate snapshots
</code_context>

<issue_to_address>
**question (testing):** Excluding `UpgradeTests` from the main CI test run might reduce coverage or hide regressions.

This step used to run the full suite (`forge test --rerun -vvvvv`), but now skips all `UpgradeTests`. If those tests cover critical behavior, removing them from CI could let regressions slip through unless another job runs them. Consider either moving `UpgradeTests` to a separate (possibly scheduled) workflow, or limiting this job to a smaller fast subset while ensuring the full suite, including `UpgradeTests`, still runs elsewhere (e.g., nightly or on releases).
</issue_to_address>

---

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.}