Skip to content

Dev/sajee/clean up#235

Merged
sajeetharan merged 2 commits into
mainfrom
dev/sajee/clean-up
Jul 20, 2026
Merged

Dev/sajee/clean up#235
sajeetharan merged 2 commits into
mainfrom
dev/sajee/clean-up

Conversation

@sajeetharan

Copy link
Copy Markdown
Collaborator

Description

Type of Change

  • 📝 New rule - Adding a new best practice rule
  • ✏️ Rule improvement - Updating an existing rule
  • 🆕 New skill - Adding an entirely new skill
  • 🐛 Bug fix - Fixing an issue with existing content
  • 📚 Documentation - Updating README, CONTRIBUTING, or other docs
  • 🔧 Build/Scripts - Changes to build process or scripts

Checklist

  • I have read the Contributing Guide
  • I ran npm run validate and it passed
  • I ran npm run build to regenerate AGENTS.md (if adding/updating rules)
  • My rule file follows the naming convention: {prefix}-{description}.md
  • My rule includes valid frontmatter (title, impact, tags)

For New Rules

Rule file: skills/cosmosdb-best-practices/rules/_____.md

Category:

Impact level:

Why is this rule important?

Agent Testing

  • Tested with GitHub Copilot
  • Tested with Claude Code
  • Tested with Cursor
  • Tested with other agent: _____
  • N/A (documentation only)

Related Issues

Additional Notes

style: enhance styles for better visual hierarchy and responsiveness

feat: redesign logo with new gradient and iconography

chore: reorganize sections in index.html for better navigation and user experience
Copilot AI review requested due to automatic review settings July 20, 2026 04:44
@sajeetharan
sajeetharan merged commit 9e7f798 into main Jul 20, 2026

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 focuses on polishing the repo’s public-facing documentation and normalizing several Cosmos DB best-practice rule writeups so they follow the preferred “Incorrect/Correct” framing, while keeping the compiled AGENTS.md output in sync.

Changes:

  • Standardizes multiple rule docs to use clearer Incorrect / Correct section headers and improves rule frontmatter consistency (e.g., impact casing, adds impactDescription where needed).
  • Updates evaluation documentation/configuration to reference Vally (including cache/container naming) instead of Waza.
  • Refreshes the GitHub Pages site (HTML/CSS + logo) with a new layout and updated installation/evaluation messaging.

Reviewed changes

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

Show a summary per file
File Description
skills/cosmosdb-best-practices/rules/throughput-container-vs-database.md Adds explicit Incorrect/Correct framing for throughput-scope guidance.
skills/cosmosdb-best-practices/rules/sdk-serialization-enums.md Normalizes impact metadata and reframes sections around Incorrect/Correct examples.
skills/cosmosdb-best-practices/rules/sdk-newtonsoft-dependency.md Reframes the rule into Incorrect/Correct sections for clarity.
skills/cosmosdb-best-practices/rules/sdk-local-dev-config.md Reframes the rule into Incorrect/Correct sections for clarity.
skills/cosmosdb-best-practices/rules/sdk-java-spring-boot-versions.md Reframes the rule into Incorrect/Correct sections for clarity.
skills/cosmosdb-best-practices/rules/sdk-etag-concurrency.md Reframes the rule into Incorrect/Correct sections for clarity.
skills/cosmosdb-best-practices/rules/sdk-emulator-ssl.md Adds explicit Incorrect/Correct framing around emulator SSL + gateway guidance.
skills/cosmosdb-best-practices/rules/pattern-efficient-ranking.md Reframes the rule into Incorrect/Correct sections for clarity.
skills/cosmosdb-best-practices/rules/index-range-vs-hash.md Adds Incorrect/Correct framing and adjusts the “modern defaults” positioning.
skills/cosmosdb-best-practices/rules/index-lazy-consistent.md Adds Incorrect/Correct framing around indexing-mode selection guidance.
skills/cosmosdb-best-practices/rules/global-consistency.md Adds Incorrect/Correct framing around consistency selection tradeoffs.
skills/cosmosdb-best-practices/AGENTS.md Regenerates compiled guidance to reflect rule doc updates.
routing-eval/README.md Updates routing-eval docs to refer to Vally-based content eval workflows.
routing-eval/layer1-acceptance/README.md Updates acceptance flow docs/links to Vally config naming.
README.md Updates repo-level evaluation instructions to use Vally CLI commands.
CONTRIBUTING.md Updates contributor testing instructions to use Vally CLI commands.
.vally.yaml Renames cache/container identifiers to Vally equivalents.
.gitignore Updates ignored cache directory to .vally-cache/.
docs/styles.css Refreshes site styling, layout, and component styles.
docs/logo.svg Replaces the site logo SVG.
docs/index.html Updates site structure/content (hero, install/coverage/workflow sections, links).

Comment on lines +12 to +13
**Incorrect (using dedicated throughput everywhere without considering sharing patterns or cost):**


Understand when to use different index types. Range indexes support equality, range, and ORDER BY; Hash indexes are deprecated.

**Incorrect (manually reasoning about deprecated hash indexes or over-specifying index kinds for standard queries):**
Comment on lines 10 to 14
Select the consistency level that matches your application's requirements. Each level has different tradeoffs for latency, availability, and consistency.

**Incorrect (defaulting to the strongest consistency level for every workload without evaluating latency and availability needs):**

**Consistency levels (strongest to weakest):**
Comment thread docs/index.html
</div>
<div class="hero-metrics">
<article>
<h2>129</h2>
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.

2 participants