Add per-language validation workflow and branch ruleset recommendations

[Copilot]

• Simplified validate.yml to match CodeQL workflow style
• Move permissions: contents: read to top-level (workflow-wide)
• Add concurrency block to cancel in-progress runs on new pushes to the same ref

Original prompt

Delegate to a seperate agent the task of creating the validation workflow. Ensure that the agent also gives me a recommendation on how to configure the repository's rulesets to ensure that it validates based on this workflow.

[Chronological Review: The conversation began with the user requesting a review of a user story and a Teams chat to develop a game plan for a draft iteration of a monorepo. The user then defined a numbering standard for samples in the repository, specifying categories and examples. The user requested to break the work into smaller pieces for delegation to a cloud agent. The user provided a list of sample repositories for context and emphasized the need for future planning in the README file. The conversation continued with the user refining the project plan, focusing on validation strategies, and simplifying the number of examples. The user ultimately requested to start the implementation by adding the project plan to the README file.]

[Intent Mapping:

1. "Help me come up with a game plan to make a v1/draft iteration of this monorepo."
2. "Let's define a numbering standard we can use for the samples repository."
3. "Help me structure this plan so I can delegate each component to a cloud agent."
4. "On day 1, I really want cloud agents to implement the table from the comment in [Azure DevOps link]."
5. "What do you recommend for validation?"
6. "Update the plan."
7. "Let's start implementation by adding the project plan to the README file."]

[Technical Inventory:

• Technologies: Azure Cosmos DB, GitHub, cloud agents.
• Patterns: Monorepo structure, incremental numbering for samples, project planning.
• Decisions: No /nosql/* subfolder, focus on language-based root subfolders, and limit examples to 2-3 per category.]

[Code Archaeology:

• File: readme.md
• Purpose: To document the project plan and structure for the samples repository.
• Current State: The user requested to add the project plan to this file, indicating the start of implementation.]

[Progress Assessment:

• Completed Tasks: Defined a numbering standard for samples, provided a list of existing samples, and discussed validation strategies.
• Partially Complete Work: Project plan needs to be added to the README file, and the implementation of the plan is pending.]

[Context Validation: All critical information for continuation is captured, including the need for a structured project plan and validation strategies.]

[Recent Commands Analysis:

• Last Agent Commands: The user requested to "start implementation by adding the project plan to the README file."
• Tool Results Summary: No specific tool results were returned as the focus was on planning and structuring the README.
• Pre-Summary State: The agent was actively working on structuring the project plan for the README file when the token budget was exceeded.
• Operation Context: These commands were executed to align the project documentation with the user's goals of creating a clear and actionable plan for the samples repository.]

1. Conversation Overview: - Primary Objectives: The user aimed to create a draft iteration of a monorepo, define a numbering standard for samples, structure a project plan for delegation to cloud agents, and implement this plan in the README file. - Session Context: The conversation flowed from initial planning to defining standards, discussing validation, and refining the project plan, culminating in a request to implement the plan in the README. - User Intent Evolution: The user's needs evolved from high-level planning to detailed implementation steps, emphasizing the importance of clarity and structure in the project documentation.

2. Technical Foundation:

• Azure Cosmos DB: A cloud database service used for building scalable applications.
• GitHub: A platform for version control and collaboration on code repositories.
• Cloud Agents: Automated agents intended to assist in implementing the project plan.

3. Codebase Status:

• File Name: readme.md
• Purpose: To document the project plan and structure for the samples repository.
• Current State: The user requested to add the project plan to this file.
• Key Code Segments: Not applicable as the focus was on planning rather than code changes.
• Dependencies: The README will guide the implementation of the samples repository.

4. Problem Resolution:

• Issues Encountered: The need for a clear validation strategy to ensure that changes in one language do not affect others.
• Solutions Implemented: Proposed a GitHub ruleset for validation to avoid merge conflicts.
• Debugging Context: Ongoing discussions about how to effectively manage sample validations across different languages.
• Lessons Learned: Importance of planning and structuring documentation for clarity and future reference.

5. Progress Tracking:

• Completed Tasks: Defined a numbering standard, discussed validation strategies, and provided a list of existing samples.
• Partially Complete ...

Created from VS Code.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[seesharprun]

The comments on how to implement the ruleset should be in the agent logs, not the README file. The readme file should include a validation section with a basic and succinct breakdown of how validation works.

[Copilot]

The comments on how to implement the ruleset should be in the agent logs, not the README file. The readme file should include a validation section with a basic and succinct breakdown of how validation...

Done in commit 0f30157. The README now has a short "Validation" section that covers only how the CI works (naming convention enforcement + path-filtered language jobs). The full ruleset setup guide (required status check names, Rulesets UI steps, classic Branch Protection fallback, CODEOWNERS template, and merge strategy) has been moved into the PR description.

[seesharprun]

The validation workflow is WAAY to complex. Can we simplify? Still use the name validation.yml or continuous-integration.yml

Here's some examples I use elsewhere:

• https://github.com/Azure-Samples/cosmos-db-nosql-dotnet-quickstart/blob/main/.github/workflows/azure-dev.yml
• https://github.com/Azure-Samples/cosmos-db-nosql-python-quickstart/blob/main/.github/workflows/azure-dev.yml
• https://github.com/Azure-Samples/cosmos-db-nosql-go-quickstart/blob/main/.github/workflows/azure-dev.yml
• https://github.com/Azure-Samples/cosmos-db-nosql-nodejs-quickstart/blob/main/.github/workflows/azure-dev.yml

[Copilot]

The validation workflow is WAAY to complex. Can we simplify? Still use the name validation.yml or continuous-integration.yml

Here's some examples I use elsewhere:...

Done in commit 10b817a. The workflow now follows the same structural style as the referenced CodeQL workflows:

• permissions: contents: read moved inside each job
• strategy: fail-fast: false added to each language job
• Removed dorny/paths-filter, concurrency, and defaults blocks
• Step names aligned (Checkout repository, Set up Python, etc.)
• Removed all error-counter bash loops — each run step is short and lets commands fail naturally
• Java updated to distribution: microsoft, .NET updated to dotnet-version: '9.0' to match the reference examples

The file went from 394 lines down to 153.