Skip to content

Standardize README prerequisites across all SDK languages#1636

Open
scottaddie wants to merge 5 commits into
mainfrom
scottaddie/readme-prerequisites
Open

Standardize README prerequisites across all SDK languages#1636
scottaddie wants to merge 5 commits into
mainfrom
scottaddie/readme-prerequisites

Conversation

@scottaddie

@scottaddie scottaddie commented Jun 11, 2026

Copy link
Copy Markdown

The .NET README listed requirements near the bottom and implied .NET 8.0 was required, which could mislead users targeting other supported .NET implementations. Other SDK READMEs also lacked consistency in how and where prerequisites were presented.

This PR standardizes prerequisites presentation across all SDK READMEs:

  • .NET: Moves the requirements content above installation as a Prerequisites section and clarifies that any .NET Standard 2.0-compatible .NET implementation is supported, linking to the Microsoft Learn compatibility guidance.
  • Node.js: Renames ## Requirements## Prerequisites and moves it before ## Installation.
  • Python: Same as Node.js.
  • Java: Promotes the ### Runtime requirements subsection (previously nested inside ## Installation) to a top-level ## Prerequisites section placed before Installation.
  • Go: Adds a new ## Prerequisites section before ## Installation listing the Go 1.24+ and CLI requirements.
  • Rust: Adds a new ## Prerequisites section before ## Quick Start listing the Rust 1.94.0+ requirement and noting the default bundled-cli behavior.

Move the .NET README requirements section above installation, rename it to prerequisites, and clarify the runtime requirement as any .NET Standard 2.0-compatible implementation.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 11, 2026 21:50
@scottaddie scottaddie requested a review from a team as a code owner June 11, 2026 21:50

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

Reorganizes the .NET SDK README to surface runtime requirements up front and clarifies framework compatibility so users don’t incorrectly infer that .NET 8 is required for all use cases.

Changes:

  • Adds a new Prerequisites section before Installation.
  • Updates wording to state support for any .NET Standard 2.0-compatible implementation and links to Microsoft Learn guidance.
  • Removes the older “Requirements” section previously located near the bottom of the README.
Show a summary per file
File Description
dotnet/README.md Moves requirements into a Prerequisites section and clarifies .NET Standard 2.0 compatibility with an external reference link.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

@github-actions

This comment has been minimized.

@scottaddie scottaddie marked this pull request as draft June 11, 2026 21:58
@scottaddie

Copy link
Copy Markdown
Author

@copilot Update this PR to also address the suggestion in #1636 (comment)

Co-authored-by: scottaddie <10702007+scottaddie@users.noreply.github.com>

Copilot AI commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@copilot Update this PR to also address the suggestion in #1636 (comment)

Done. Applied the consistent ## Prerequisites pattern across all SDK READMEs in commit Apply consistent Prerequisites sections across all SDK READMEs:

  • Node.js: renamed ## Requirements## Prerequisites, moved before ## Installation
  • Python: same as Node.js
  • Java: promoted the ### Runtime requirements subsection (inside Installation) to a top-level ## Prerequisites section placed before Installation
  • Go: added a new ## Prerequisites section before ## Installation listing Go 1.24+ and CLI requirements
  • Rust: added a new ## Prerequisites section before ## Quick Start listing Rust 1.94.0+ and noting the bundled-cli default

Copilot AI changed the title Clarify .NET README prerequisites Standardize README prerequisites across all SDK languages Jun 11, 2026
@scottaddie scottaddie marked this pull request as ready for review June 11, 2026 22:06
@github-actions

This comment has been minimized.

@github-actions github-actions Bot 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.

Generated by SDK Consistency Review Agent for issue #1636 · sonnet46 871.4K

Comment thread python/README.md Outdated
@scottaddie

Copy link
Copy Markdown
Author

@copilot update this PR to address the suggestions in #1636 (comment)

Co-authored-by: scottaddie <10702007+scottaddie@users.noreply.github.com>

Copilot AI commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@copilot update this PR to address the suggestions in #1636 (comment)

Done. Updated python/README.md to change "GitHub Copilot CLI installed and accessible" to "GitHub Copilot CLI installed and in PATH (or provide a custom connection=RuntimeConnection.for_stdio(path=...))". This now matches the specificity pattern used by all other SDK READMEs.

@github-actions

This comment has been minimized.

@scottaddie

Copy link
Copy Markdown
Author

@copilot update this PR to address the pre-existing nit mentioned in #1636 (comment)

Co-authored-by: scottaddie <10702007+scottaddie@users.noreply.github.com>

Copilot AI commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@copilot update this PR to address the pre-existing nit mentioned in #1636 (comment)

Fixed in the latest commit — removed the stray trailing period from 1.0.55-5.1.0.55-5 in java/README.md.

@github-actions

This comment has been minimized.

@scottaddie

Copy link
Copy Markdown
Author

@copilot update the PR to address the minor nitpick mentioned in #1636 (comment)

Co-authored-by: scottaddie <10702007+scottaddie@users.noreply.github.com>

Copilot AI commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@copilot update the PR to address the minor nitpick mentioned in #1636 (comment)

Done. Updated Node.js, Python, and .NET Prerequisites sections to use `PATH` (code-formatted), matching Go and Java.

@github-actions

Copy link
Copy Markdown
Contributor

Cross-SDK consistency review ✅

This PR now covers all six SDK READMEs consistently. Here is the final cross-SDK analysis of the current head:

SDK Section heading Position Runtime requirement CLI requirement PATH formatting
Node.js ## Prerequisites Before Installation ✅ Node.js version
Python ## Prerequisites Before Installation ✅ Python version
Go ## Prerequisites Before Installation ✅ Go version
.NET ## Prerequisites Before Installation ✅ .NET Standard 2.0+
Java ## Prerequisites Before Installation ✅ Java version
Rust ## Prerequisites Before Quick Start ✅ Rust version N/A (bundled-cli)

All SDKs now:

  • Use ## Prerequisites as the section name
  • Place the section before the first actionable section (Installation / Quick Start)
  • List both the language runtime version requirement and the CLI requirement
  • Use `PATH` (backtick-formatted) consistently where applicable

Rust's CLI bullet uses a different structure (bundled-cli feature first, then COPILOT_CLI_PATH as override) — this is appropriate given the Rust SDK's unique bundled-CLI capability and doesn't represent an inconsistency.

Pre-existing note (not introduced by this PR): java/README.md is the only SDK that specifies a minimum CLI version (1.0.55-5 or later). The other READMEs omit a minimum CLI version floor. Worth aligning in a follow-up if desired, but out of scope here.

Generated by SDK Consistency Review Agent for issue #1636 · sonnet46 1.1M ·

Comment thread dotnet/README.md

## Prerequisites

- Any of the [.NET Standard 2.0-compatible .NET implementations](https://learn.microsoft.com/dotnet/standard/net-standard?tabs=net-standard-2-0#select-net-standard-version)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Building the SDK, which I expect what this is intending to refer to, actually requires a .NET 10 SDK or later.

@stephentoub stephentoub left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Other than the .NET issue, LGTM

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.

4 participants