Repository navigation
fix(release): normalize source build script line endings - #11
Merged
Merged
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
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.
The release workflow exposed CRLF line endings in
scripts/build_ffmpeg_source.shfrom a Windows checkout, causing Bash to rejectset -o pipefailon Ubuntu.This normalizes the build script to LF, adds
.gitattributesso shell scripts stay LF across platforms, and adds abash -ncheck to Android CI so the source-build entrypoint is validated before merge.The normalized script blob matches the local LF Git object SHA. The Android CI run will verify the shell syntax and project checks.