chore: fix handling of multi-line COMMITS
variable
#662
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.
Please go through the following checklist
!
is used if and only if at least one breaking change has been introduced.source scripts/run_ci_checks.sh
.source scripts/check_commits.sh
, and the commit history is certified to follow clean commit guidelines as described here: https://github.com/spaceandtimelabs/sxt-proof-of-sql/blob/main/COMMIT_GUIDELINES.mdmain
have been incorporated into this PR by simple rebase if possible; if not, then conflicts are resolved appropriately.Rationale for this change
The
COMMITS
variable stores multiple lines, but it's passed into<<<
, which can lead to incorrect handling of multi-line input. This could cause issues when processing commit messages.What changes are included in this PR?
<<< "$COMMITS"
with awhile read
loop using process substitution< <(...)
.Are these changes tested?
Yes, tested with different commit histories to confirm correct behavior. Let me know if further validation is needed! 🚀