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
1 participant
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 CI commit from the Makefile branch landed after PR #2 was merged (same story as PR #1), so it never triggered a run; re-proposed from a fresh main.
lintjob: shellcheck over the shell entry points on ubuntutestjob: golden + integration suites on ubuntu and macos; Linux exercises a different awk (gawk verified byte-identical locally) and an older tmux, macOS matches the reference environmentLC_ALL=en_US.UTF-8is pinned at workflow level: runners default to C/C.UTF-8, where macOS awk's collation quirk (all Cyrillic letters compare equal under ==) would not reproduce, so without the pin the macos leg would not actually guard against it