Skip to content

Conversation

@AlvaradoVallejo
Copy link

@AlvaradoVallejo AlvaradoVallejo commented Nov 21, 2025

Note

Updates the Tests workflow to run on push/PR, pin Foundry to 1.2.0, add caching, and standardize test execution.

  • CI Workflow (.github/workflows/Tests.yml):
    • Triggers: Run on pushes to master/develop and on pull_request.
    • Job: Rename to "Foundry Tests".
    • Checkout: Use actions/checkout@v4 with recursive submodules.
    • Toolchain: Pin foundry-rs/foundry-toolchain@v1 to version: '1.2.0'.
    • Caching: Add actions/cache@v4 for ~/.foundry/cache, ./cache, and ~/.cargo/bin/.
    • Tests: Run forge test -vv (reduced verbosity from -vvv).

Written by Cursor Bugbot for commit cebfa61. This will update automatically on new commits. Configure here.

version: nightly
# CRITICAL: Lock to a specific stable version (e.g., 1.2.0)
# instead of the unstable 'nightly'. Replace with the project's supported version.
version: '1.2.0'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Hardcoded Foundry version appears to be placeholder text

The Foundry version is hardcoded to 1.2.0 with a comment that reads "Replace with the project's supported version." This appears to be placeholder template code that wasn't completed before committing. The comment explicitly indicates this value should be replaced with the actual version the project supports, not left as the example value.

Fix in Cursor Fix in Web

branches:
- master # Run on push to master branch
- develop # Optional: Include development branches
pull_request: # CRITICAL: Ensure tests run when a PR is opened/updated
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Pull request trigger missing branch filter

The pull_request trigger is configured without a branches filter, while the push trigger restricts to master and develop branches. This creates an inconsistency where pull requests to any branch will trigger tests, but direct pushes only trigger on specific branches. Either the pull_request trigger should also specify branch restrictions, or the configuration intent needs clarification.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant