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.
This pull request includes changes to the GitHub Actions workflow files
.github/workflows/fuzzing.yml
and.github/workflows/main.yml
. The changes mainly involve the modification of the fuzzing workflow, including the change of permissions, scheduling, and the use of environment variables instead of inputs. The most important changes are:.github/workflows/fuzzing.yml
: Permissions for the fuzzing workflow have been changed from read to write..github/workflows/fuzzing.yml
: The trigger for the fuzzing workflow has been changed from a workflow call to a daily schedule at 21:00 UTC and a manual dispatch..github/workflows/fuzzing.yml
: The use of inputs has been replaced with environment variables. This change affects the platform and architecture parameters used in the workflow, as well as several conditionals and commands within the workflow. [1] [2] [3] [4] [5].github/workflows/fuzzing.yml
: The repository URL used when pushing updates to the fuzzing corpus has been changed to use thegithub.repository
context instead of a hardcoded repository URL..github/workflows/main.yml
: The reference to the fuzzing workflow has been removed.These changes seem to aim at making the fuzzing workflow more autonomous and flexible, by allowing it to run on a schedule or manually, and by using environment variables instead of inputs.