Fix uninitialized my_array variable in the script Update dco_check.sh #7898
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.
PR description
This pull request addresses an issue where the
my_array
variable was not initialized at the beginning of the script. The variable was used for accumulating branch names, but it wasn't explicitly initialized, which could lead to potential errors or unexpected behavior when the script is executed.Fix Summary:
my_array
: The arraymy_array
has now been initialized before its usage. This ensures that the array is properly set up and avoids any issues when appending values to it.Signed-off-by
line.Importance of the fix:
This change improves the reliability of the script and ensures that it will work as intended across various systems.
Thanks for sending a pull request! Have you done the following?
doc-change-required
label to this PR if updates are required.Locally, you can run these tests to catch failures early:
./gradlew build
./gradlew acceptanceTest
./gradlew integrationTest
./gradlew ethereum:referenceTests:referenceTests