This policy explains how LinearCli.com selects sources, checks technical claims, presents commands, handles updates and protects its independence.
LinearCli.com covers Linear CLI installation, authentication, configuration, commands, workflows, integrations, comparisons and troubleshooting.
Content should explain what a command does, what it requires, what result the user should expect and which limitations may affect the outcome.
Core principle: Never ask a user to copy a command without providing enough context to understand its purpose.
Technical claims are stronger when they can be checked against the source that defines the feature or command.
These sources are used first when confirming syntax, supported features and current behavior.
Secondary sources can provide context but should not replace available primary documentation.
Unsupported material is not treated as reliable technical evidence.
A useful command example must include syntax, prerequisites, context and a realistic expected result.
Check the command name, subcommand, flags, arguments and example values.
State whether installation, authentication, configuration, Git or another tool is required.
Clarify whether the command should run globally, inside a repository or from a configured project.
Tell users what a successful result should look like and what to check when it fails.
Technical accuracy is important, but the information must also be readable and safe to follow.
Explain unfamiliar terms before relying on them in instructions.
Commands appear in clear code blocks so users can distinguish executable text from supporting content.
Placeholder issue IDs, workspace names and project values should not be mistaken for universal settings.
Dependencies, permission requirements and unsupported environments should be visible.
API keys, access tokens and private workspace information must never be requested by this website.
Pages should be reviewed when meaningful changes affect commands, installation methods, authentication or user outcomes.
A command is added, removed or renamed.
An installation method or requirement changes.
Authentication or credential handling changes.
A documented workflow produces a different result.
A material factual or safety issue is identified.
LinearCli.com does not label a page as “latest” merely because a year has changed. Update wording should reflect an actual content review.
When a factual, technical or safety-related error is identified, the affected instruction should be checked against reliable sources and corrected.
Independent documentation should make its relationship to the products it discusses immediately understandable.
LinearCli.com is not affiliated with or endorsed by Linear or the developer of the Linear CLI software.
This website does not connect to a Linear workspace, execute commands or receive API keys.
Any future sponsorship or commercial relationship that could affect user interpretation should be clearly labelled.
AI tools may assist with organization or drafting, but their output is not treated as a technical source and should be checked before publication.
Operating systems, shells, package managers, permissions, repository settings and software versions can change a command’s result. Users should review commands before running them and protect their own credentials and data.
Review the purpose of LinearCli.com or continue to practical command documentation.