Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PYD-1399: Add environments documentation #591

Merged
merged 22 commits into from
Nov 14, 2024

typo

9de9e92
Select commit
Loading
Failed to load commit list.
Merged

PYD-1399: Add environments documentation #591

typo
9de9e92
Select commit
Loading
Failed to load commit list.
Hyperlint AI / Hyperlint Style Guide succeeded Nov 14, 2024 in 5s

👏 No style guide issues found.

2 files reviewed, no outstanding issues found.

Details

📄 docs/guides/advanced/index.md

LineIssuesTextComment
7(Spelling-error) Did you really mean 'dev'?Existing:
* **[Using Environments](using-environments.md):** Group data between environments (e.g. dev, staging, prod) within a project.
The term 'dev' is a widely accepted shorthand for 'development' in technical contexts, particularly when referring to different environments. It is not a spelling error but a common industry term. Therefore, no change is necessary.

📄 docs/guides/advanced/using-environments.md

LineIssuesTextComment
54(Spelling-error) Did you really mean 'dev'?Existing:
for details). So if you need to allow different team members to view dev vs. prod traces, then projects would be a better fit.
The term 'dev' is a widely accepted shorthand for 'development' in technical contexts. Unless the style guide specifically prohibits such shorthand, it is generally acceptable to use 'dev' in this context. No change is necessary.

🪄 About Hyperlint

Hyperlint is your AI-powered copilot for creating high-quality documentation with minimal effort.

Sign up for a free plan at hyperlint.com.