Repository navigation
chore(workflows): share current formatter defaults - #11
Merged
Merged
Conversation
Use the published Studio format preset for the repository's existing formatting commands and staged-byte adapters. Keep genuine native style files authoritative and pin the formatter engines used by local checks. Prepare the exact shared package, Prettier and Ruff during setup with a real dependency lock. Commit hooks use verified cached tools and retain staged, unstaged and unrelated content when formatting fails. Co-authored-by: Codex <noreply@openai.com>
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.
TL;DR
Use the published Studio formatting preset and current formatter engines for repository source and configuration. Keep native style files authoritative while local commands and commit hooks use the same reviewed pins.
Changes
@thehypertextstudio/format-configthrough a thin repository config; retain existing native styles and genuine parser plugins.Validation: Swift/native-addon tests pass, including Terraform stdin formatting and invalid-source rejection. Shared-preset imports resolve to the same configuration across all 14 native repositories. Four representative installed-hook commit fixtures pass; this does not establish every repository’s full CI acceptance.
Follow-ups and Next Work
Retain the existing product build and release acceptance gates.