Skip to content

General contributing maintenance - #579

Merged
Lauren Hirata Singh (lnhsingh) merged 2 commits into
mainfrom
copilot
Sep 18, 2025
Merged

General contributing maintenance#579
Lauren Hirata Singh (lnhsingh) merged 2 commits into
mainfrom
copilot

Conversation

@lnhsingh

Copy link
Copy Markdown
Collaborator

Overview

  • Update Copilot instructions for better reviews
  • Move conceptual guides to /oss/concepts dir and update cross-references
  • Add info the the README about code language fences

Type of change

Type: Update existing docs

Related issues/PRs

  • GitHub issue:
  • Feature PR:
  • Linear issue:
  • Slack thread:

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
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed
  • I have gotten approval from the relevant reviewers
  • (Internal team members only / optional) I have created a preview deployment using the Create Preview Branch workflow

Additional notes

Copilot AI review requested due to automatic review settings September 18, 2025 15:27
@github-actions github-actions Bot added langchain For docs changes to LangChain langgraph For docs changes to LangGraph langgraph-platform oss labels Sep 18, 2025

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR performs general maintenance on the documentation repository by updating Copilot instructions for better reviews, reorganizing conceptual guides into a new /oss/concepts directory, and adding information about code language fences to the README.

  • Update GitHub Copilot instructions with improved folder structure and style guide information
  • Move conceptual guides (Memory, Context, Subgraphs) to /oss/concepts directory and update all cross-references
  • Add documentation about custom code language fences to README

Reviewed Changes

Copilot reviewed 19 out of 21 changed files in this pull request and generated no comments.

Show a summary per file
File Description
.github/copilot-instructions.md Update folder structure documentation and add style guide information
README.md Add section on custom code language fences and improve formatting
src/oss/learn.mdx Update links to conceptual guides in new /concepts directory
src/oss/contributing/documentation.mdx Update example page links to new conceptual guide locations
src/oss/concepts/context.mdx Update internal cross-references to memory guide
Multiple LangGraph files Update cross-references to subgraphs and memory guides in new locations
Multiple LangGraph Platform files Update cross-references to memory and subgraphs guides
src/oss/langchain/agents.mdx Update memory guide reference

@github-actions

Copy link
Copy Markdown
Contributor

Preview ID generated: preview-copilo-1758209315-e7fbcac

@katmayb Kathryn May (katmayb) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just had one question about code block docs syntax depending on OSS / Commercial docs. But otherwise LGTM!

Comment on lines +70 to +72
We have implemented custom code language fences for Python and Javascript. They are used to tag content that is specific to that language. Use either `:::python` or `:::js` to tag content that is specific to that language. Both are closed with the `:::` fence.

If any code fences like this exist on the code page, then two outputs (one for each language) will be created. For example, if this syntax is on the page in `/concepts/foo.mdx`, two pages will be created at `/python/concepts/foo.mdx` and `/javascript/concepts/foo.mdx`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if this is only referring to the OSS docs, but is it confusing that in LangSmith / Platform we're using CodeGroup even though there are often Python / JavaScript code blocks for examples (rather than wanting two separate files).

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think ideally, we use CodeGroup and keep one set of docs. The custom language fences are more because the prose / descriptions are also different (not just code samples). I'll clarify here that we only use this fencing in OSS docs

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK cool, thanks!

@github-actions

Copy link
Copy Markdown
Contributor

Preview ID generated: preview-copilo-1758213608-d8f406a

@lnhsingh
Lauren Hirata Singh (lnhsingh) merged commit d228459 into main Sep 18, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

langchain For docs changes to LangChain langgraph For docs changes to LangGraph oss

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants