refactor: move forge test intense workflow into separate file #391
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nadir-akhtar
force-pushed
the
nadir/adjust-intense-test-workflow
branch
from
7b28c69 to
774ff7e
Compare
stevennevins
approved these changes
Feb 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, the
Forge Test (Intense)workflow runs on every PR. However, the results of this workflow are not helpful for deciding whether to merge PRs, as the Intense workflow is designed for continuous fuzzing on an infrequent (e.g. once per day) basis. As such, this creates noise when reviewing PRs.Changes
Forge Test (Intense)workflow with its own triggers, moving the functionality out of.github/workflows/foundry.ymlImpact