langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 20:35:34 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #2153] [MERGED] fix: correct indentation in langsmith/cli.mdx #2176

New Issue
Closed
opened 2026-02-17 17:23:08 -05:00 by yindo · 0 comments
yindo commented 2026-02-17 17:23:08 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/2153
Author: @happyphper
Created: 1/9/2026
Status: ✅ Merged
Merged: 1/22/2026
Merged by: @lnhsingh

Base: main ← Head: fix/table-indentation-cli

📝 Commits (1)

  • 83040d8 fix: correct indentation in langsmith/cli.mdx

📊 Changes

1 file changed (+27 additions, -27 deletions)

View changed files

📝 src/langsmith/cli.mdx (+27 -27)

📄 Description

Overview

This PR fixes formatting inconsistencies in one LangSmith documentation files:
Corrects tab-based indentation in markdown tables within src/langsmith/cli.mdx, replacing tabs with spaces for consistent rendering across different markdown parsers.

Type of change

Type: Fix typo/bug/link/formatting

Related issues/PRs

  • GitHub issue: None
  • Feature PR: None
  • Linear issue: N/A
  • Slack thread: N/A

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly (N/A - formatting changes only)
  • I have used root relative paths for internal links (N/A - no link changes)
  • I have updated navigation in src/docs.json if needed (N/A - no navigation structure changes)

(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow

Additional notes

  • Used targeted sed replacements instead of automated formatters to avoid unintended changes
  • Tab characters were replaced with 4 spaces to match project's indentation style
  • Verified changes by:
    1. Running cat -A to visualize non-printable characters
    2. Previewing in local development server
    3. Checking markdown rendering in VS Code preview
  • These fixes ensure consistent display across different markdown parsers and editors

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/2153 **Author:** [@happyphper](https://github.com/happyphper) **Created:** 1/9/2026 **Status:** ✅ Merged **Merged:** 1/22/2026 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `main` ← **Head:** `fix/table-indentation-cli` --- ### 📝 Commits (1) - [`83040d8`](https://github.com/langchain-ai/docs/commit/83040d8d2dbe3c500a401b547caf1a7469e027a8) fix: correct indentation in langsmith/cli.mdx ### 📊 Changes **1 file changed** (+27 additions, -27 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/cli.mdx` (+27 -27) </details> ### 📄 Description ## Overview This PR fixes formatting inconsistencies in one LangSmith documentation files: Corrects tab-based indentation in markdown tables within `src/langsmith/cli.mdx`, replacing tabs with spaces for consistent rendering across different markdown parsers. ## Type of change **Type:** Fix typo/bug/link/formatting ## Related issues/PRs <!-- No related issues found. These formatting issues were identified during code review. To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: None - Feature PR: None <!-- For LangChain employees, if applicable: --> - Linear issue: N/A - Slack thread: N/A ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly (N/A - formatting changes only) - [ ] I have used **root relative** paths for internal links (N/A - no link changes) - [ ] I have updated navigation in `src/docs.json` if needed (N/A - no navigation structure changes) (Internal team members only / optional): Create a preview deployment as necessary using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes - Used targeted `sed` replacements instead of automated formatters to avoid unintended changes - Tab characters were replaced with 4 spaces to match project's indentation style - Verified changes by: 1. Running `cat -A` to visualize non-printable characters 2. Previewing in local development server 3. Checking markdown rendering in VS Code preview - These fixes ensure consistent display across different markdown parsers and editors --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-17 17:23:08 -05:00
yindo closed this issue 2026-02-17 17:23:09 -05:00
yindo changed title from [PR #2153] fix: correct indentation in langsmith/cli.mdx to [PR #2153] [MERGED] fix: correct indentation in langsmith/cli.mdx 2026-06-05 18:17:05 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#2176
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?