chore: establish prettier baseline#416
Open
anirudh5harma wants to merge 1 commit into
Open
Conversation
Collaborator
|
hey @anirudh5harma the reverbCode has been ported to : https://github.com/AgentWrapper/agent-orchestrator. Please port your PRs there. |
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
2 participants
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.
Summary
Closes #417.
Feature PRs no longer inherit unrelated formatting churn from files that were already off-baseline on
main.This establishes the current Prettier baseline for human-authored files and extends
.prettierignoreso the formatter does not rewrite generated TanStack route output or the pnpm lockfile. That keeps the existing auto-format workflow focused on actual branch changes instead of adding broad docs/generated/lockfile noise to unrelated PRs.Tests
npx --yes prettier@3 --check .git diff --check