Add CI pipeline checks to verify code formatting for TypeSpec, Markdown, and Rust files

[Copilot]

This PR implements comprehensive CI formatting checks to ensure all TypeSpec, Markdown, and Rust source code follows the defined prettier and rustfmt rules, integrated with the existing Azure DevOps pipeline.

What's Added

Azure DevOps Integration

• eng/pipelines/templates/steps/build-test.yaml - Added formatting checks to existing CI pipeline
• eng/pipelines/templates/steps/set-env.yaml - Added prettier installation
• Runs after the lint step in the existing pipeline structure

Developer Scripts

• scripts/check-all-formats.sh - Comprehensive format checking for all file types
• scripts/format-all.sh - Auto-format all supported files
• scripts/check-rust-format.sh - Rust-specific formatting with proper edition handling
• scripts/check-typespec-format.sh - TypeSpec file validation (prettier parser not available)

Package Integration

Updated packages/typespec-rust/package.json with:

• Prettier dependency for consistent formatting
• New npm scripts: format, format:check, format:prettier, format:eslint
• Zero-warnings policy for ESLint checks

Configuration

• .prettierignore - Excludes generated code, build artifacts, and .tsp files
• .editorconfig - Consistent formatting rules across different editors to prevent unnecessary whitespace changes
• Preserves existing configurations (.prettierrc, eslint.config.js, rust-toolchain.toml)

Documentation

• .github/copilot-instructions.md - Added guidance on source regeneration and testing procedures including TypeSpec compilation, running tests, and operating the spector server

Usage

Local Development:

# Check all formatting
./scripts/check-all-formats.sh

# Auto-format all files
./scripts/format-all.sh

# Package-specific commands
cd packages/typespec-rust
pnpm run format:check    # Check formatting
pnpm run format          # Fix formatting

Source Generation and Testing:

cd packages/typespec-rust
pnpm run tspcompile      # Regenerate Rust code from TypeSpec
pnpm run test            # Run TypeScript tests
pnpm run spector --serve # Run spector server for testing

CI Pipeline:

• Automatically runs on all pushes and pull requests
• Must pass before code can be merged
• Provides clear feedback on formatting violations

File Type Coverage

File Type	Tool	Status
TypeScript/JavaScript	ESLint	✅ Zero warnings enforced
Markdown/JSON	Prettier	✅ Formatting validated
Rust	rustfmt	✅ Edition 2021, excludes generated code
TypeSpec	Custom validation	✅ Basic syntax validation

The implementation handles edge cases like generated test files with Rust edition conflicts and provides clear error messages for developers.

Fixes #516.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[LarryOsterman]

The CI pipeline for this repo is an Azure DevOps pipeline, not a github workflow. Please fix this PR so it works with the existing pipeline.

[Copilot]

The CI pipeline for this repo is an Azure DevOps pipeline, not a github workflow. Please fix this PR so it works with the existing pipeline.

Fixed! I've removed the GitHub Actions workflow and integrated the formatting checks into the existing Azure DevOps pipeline structure instead. The changes are in commit 8ebcc4f:

• Removed .github/workflows/format-check.yml
• Added formatting checks to eng/pipelines/templates/steps/build-test.yaml
• Added prettier installation to eng/pipelines/templates/steps/set-env.yaml
• Applied consistent formatting to all existing code files

The formatting validation now runs as part of the existing CI pipeline after the lint step.

[LarryOsterman]

/azp run Azure.typespec-rust

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[LarryOsterman]

There appear to be CI pipeline errors related to formatting.

[Copilot]

There appear to be CI pipeline errors related to formatting.

Fixed the CI formatting errors! The issue was a conflict between Prettier and ESLint indentation rules. I've resolved it by disabling the ESLint indent rule (which conflicts with Prettier) and applied proper formatting to the affected files. All formatting checks now pass. See commit 7b1afed.

[LarryOsterman]

/azp run Azure.typespec-rust

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull Request Overview

This PR implements comprehensive CI formatting checks to ensure all TypeSpec, Markdown, and Rust source code follows defined formatting rules. The implementation includes GitHub Actions workflows, developer scripts, and package integration to enforce consistent code style across the project.

Key Changes

• Automated CI pipeline checks for TypeScript/JavaScript (ESLint), Markdown/JSON (Prettier), Rust (rustfmt), and TypeSpec files
• Developer scripts for local formatting validation and auto-formatting
• Package integration with new npm scripts and Prettier dependency

Reviewed Changes

Copilot reviewed 37 out of 51 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
scripts/format-all.sh	Auto-format all supported files with appropriate tools
scripts/check-all-formats.sh	Comprehensive format checking for all file types
scripts/check-rust-format.sh	Rust-specific formatting validation with edition handling
scripts/check-typespec-format.sh	TypeSpec file validation (basic syntax checking)
packages/typespec-rust/package.json	Added Prettier dependency and formatting npm scripts
packages/typespec-rust/eslint.config.js	Disabled indent rule to avoid conflicts with Prettier
Multiple TypeScript files	Applied consistent formatting using ESLint and Prettier
Documentation files	Updated formatting and added development workflow instructions

Files not reviewed (1)

• packages/typespec-rust/pnpm-lock.yaml: Language not supported

[heaths]

Moving PRs we don't want for the release today to draft. @copilot, please rebase this PR.

[Copilot]

Moving PRs we don't want for the release today to draft. @copilot, please rebase this PR.

I'm unable to perform a git rebase operation due to environment limitations - force push is not available in my sandbox environment. Additionally, I can't fetch the latest changes from the remote due to authentication restrictions.

Could you clarify what specific changes you'd like me to make? I can:

• Make new commits with changes
• Reset and recreate commits (if you specify what should be included)
• Reorganize the code changes

What would be the preferred approach for updating this PR?

[RickWinter]

@copilot rebase the changes with main.

[Copilot]

@copilot rebase the changes with main.

I'm unable to perform a git rebase operation due to environment limitations - force push is not available in my sandbox environment. Could you clarify what specific changes you'd like me to make? I can make new commits with changes or reorganize the code changes in another way.

[RickWinter]

@copilot merge with main

[Copilot]

@copilot merge with main

I'm unable to perform a git merge with main due to environment limitations - I cannot fetch from the remote repository due to authentication restrictions, and force push operations are not available in my sandbox environment.

Could you clarify what specific changes you'd like me to make instead? I can:

• Make new commits with updated changes
• Modify specific files if there are conflicts you'd like me to resolve
• Reorganize the code changes in another way

What would be the preferred approach for updating this PR?