Repository navigation
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 README new-locale command writes to
humanize/locale, although the source checkout stores catalogs undersrc/humanize/locale. It also requires the destination directory to exist.Changes proposed in this pull request:
msginit.LC_MESSAGESdirectory before generating the catalog.Validation: in an isolated temporary checkout, reproduced
msginitfailing on the old output path. Executed the corrected README commands withcs_CZand--no-translatorfor noninteractive validation; the catalog was created at the source path and passedmsgfmt --check. Generated existing translation binaries and ran the full suite: 854 passed, 2 skipped.prek run --all-filespasses.AI assistance: prepared and verified with OpenAI Codex.