Skip to content

Clarify ty check output format default in CLI doc#478

Closed
brainwane wants to merge 1 commit intoastral-sh:mainfrom
brainwane:cli-guidance
Closed

Clarify ty check output format default in CLI doc#478
brainwane wants to merge 1 commit intoastral-sh:mainfrom
brainwane:cli-guidance

Conversation

@brainwane
Copy link
Contributor

Summary

Add a "[default]" note in the CLI documentation to indicate that, by default, ty check prints "full" diagnostic output, not "concise" output.

Test Plan

I pushed the branch, and read the preview of the Markdown file on GitHub in my browser.

@AlexWaygood
Copy link
Member

Thanks! Unfortunately this particular file is generated from a MarkDown file found in the Ruff repo (https://github.com/astral-sh/ruff/blob/main/crates/ty/docs/cli.md) -- you'd have to edit that file to make changes to these docs. Sorry about this, I know it's a pretty unusual setup :-(

@brainwane brainwane deleted the cli-guidance branch May 22, 2025 12:09
sharkdp pushed a commit that referenced this pull request May 23, 2025
…490)

## Summary

Explain in `CONTRIBUTING.md` that some ty help text and reference
documentation result from source code that lives in Ruff, and point to
sources, to help tech writer contributors.

Inspired by my stumble in #478 and subsequent pointers in
astral-sh/ruff#18246 .

## Test Plan

I used `git grep` to search the Ruff repository for several chunks of
the prose in `docs/reference/` to verify which source code contains text
that turns into the autogenerated docs. I pushed my branch to GitHub and
manually checked that the formatting and hyperlinks were correct.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants