Repository navigation
chore(templates): sync dev to stable - #929
Merged
Merged
Conversation
Add CODEOWNERS so every PR targeting template/pre-release is gated on at least one approval from Yimin-Jin or huimiu (combined with the branch's require_code_owner_reviews protection rule, enabled separately).
Make the workflow_dispatch `commit_sha` input optional. When the user leaves it blank, a new `Resolve commit SHA` step queries the GitHub API for the current tip of `microsoft-foundry/foundry-samples@main` and pins the catalog generation to that SHA. - `commit_sha`: required=false, default empty. - New step uses `gh api` (default GITHUB_TOKEN, contents:read is enough for a public repo) and validates the result looks like a SHA before using it. - The pinned SHA + its source (user input vs. resolved-from-main) is echoed to the step summary so reviewers can see what the run targeted. - `Generate sample catalog` now reads from `steps.resolve-sha.outputs.sha` instead of `inputs.commit_sha` directly.
Sync activity template from stable
Publish the reviewed 89-template/44-card snapshot as one schema-v2 catalog, with source definitions, deterministic validation, and a pinned sync workflow. Intentionally restore the reviewed source SHA for template/dev, excluding ten entries from the newer development snapshot. Preserve upstream generator improvements.
Pin the unified catalog to the stable 105-template snapshot. Absorb eight additions into five existing cards and group the remaining eight into six cards. Preserve every existing card membership and enforce unique language/framework/protocol selection with regression tests.
Reuse generatedAt when the complete catalog content is unchanged. Add a deterministic repeated-scan regression test and verify source, template, and card changes retain their new generation timestamp.
Preserve surviving metadata and card content, remove deleted samples, and reuse the existing AI helper for new template metadata and compatible card placement. Enforce per-card tuple uniqueness, validate both outputs before publishing, and make the sync Action submit both files without refresh controls. Add mocked incremental CLI coverage and keep reviewed catalog data unchanged.
Derive tree, manifest and README endpoints from a validated GitHub source URL. Skip surviving override entries during incremental reconciliation while retaining deleted/unknown warnings. Add regression coverage for configured forks, invalid URLs, and override preservation.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…802) * Update solution template descriptions and curated tags * Move solution catalog alongside hosted agent sample catalog * Remove solution catalog schema version metadata
…804) * Update solution template descriptions and curated tags * Move solution catalog alongside hosted agent sample catalog * Remove solution catalog schema version metadata
Copy the same six hosted-agent catalog data and generator files from template/dev at 02e821a. Align pre-release to 105 templates, 50 cards and 13 patterns at sample revision 3d734b93b66f163bea9886d73c6808adc32e68fc. Preserve legacy client schema compatibility; explicitly retire the 03-mcp path absent from that sample revision.
Handle finish_reason=length in the shared AI request loop by increasing the per-call completion budget up to an automatic 16,000-token ceiling, bounded by existing attempt limits. Reject truncated responses even if their JSON parses; preserve explicit reasoning settings and stop without writing catalogs on exhaustion. Add offline regression coverage for metadata/card-placement recovery and budget, refusal, and API-error boundaries.
Allocate deterministic suffixes for new AI-proposed card IDs while preserving published/retired IDs and tuple constraints. Add collision regression coverage and a validation-only workflow mode that skips write tokens, branch publishing and PR creation, uploading checked catalog artifacts instead.
Review final memberships once after grouping, using pinned READMEs for both existing and new implementations. Accept only sparse validated Details patches while preserving card identities and unchanged text. Retain strict per-card language/framework/protocol uniqueness and stop publication on missing evidence or invalid review output. Keep validated data artifacts for branch-scoped generated Draft PR review.
Keep sample-catalog.json limited to legacy template fields and publish schema, patterns, grouping and Details only in sample-cards.json. Preserve the existing snapshot and card ordering; keep catalog bytes and timestamp unchanged for card-only edits. Update writer, sync instructions and regression tests for the two-document contract.
Publish cards with sourceCommitSha, patterns and cards only. Preserve explicit card order without a version discriminator. Retain structural, ownership and unique-selection validation and ensure generation remains idempotent.
Review proposed new cards against compatible same-Pattern candidates before creating them. Audit every Details field with validated README quotes, preserve meaningful Requirements, and qualify variant-specific claims. Cover successful and rejected incremental-sync paths without editing generated data.
Supply numbered pinned README excerpts to reuse and Details reviews and resolve references to exact source text in code. Reject unknown paths, invalid IDs and model-provided quotes before writing either catalog. Cover Markdown preservation and failure atomicity in incremental CLI tests.
Keep template facts and card definitions logically separate within sample-catalog.json. Write and publish only that validated snapshot, preserve evidence-backed incremental review and idempotency, and remove the companion file and split-format test/workflow contracts.
Promote the exact catalog and generator snapshot from template/dev@8c2baae6, including reviewed PR #819 corrections and the single-file migration from #818. Remove the obsolete cards sidecar and preserve pre-release CODEOWNERS. Exclude the unmerged autonomous-verifier experiment. Verified exact source equivalence and 102 passing tests.
Add an on-demand repository skill for the agreed CI-generated Draft PR followed by human-led AI review. Define snapshot and structural checks, per-implementation semantic standards, minimal authorized data fixes, validation and release-promotion boundaries. Reference current code rather than hard-coded counts or versions; do not change the sync workflow.
Split incremental generation into resumable stages and append a sandboxed Copilot skill review to the same Draft PR workflow. Keep repository and model credentials outside the agent, constrain prose patches and pinned-source evidence, and publish via non-force Git ref updates after trusted validation. Add offline container smoke coverage and 123 passing regression tests.
Constrain review references to supplied README sources and retry evidence validation failures with bounded corrective feedback. Preserve strict publication checks and original model responses. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Reuse the existing pure Details validator inside the bounded model correction loop. Address the action/patch mismatch found by the first real branch workflow run without weakening publication checks or retrying incompatible-card decisions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Retain the validated dev catalog review fixes while joining the independently promoted stable history. The resulting tree is identical to the existing dev head. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Retain the validated dev catalog scripts and tests. Preserve the existing code-owner rules and use a branch-neutral comment so both promotion targets can share the resolution. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sync the current
template/devbranch intotemplate/stable.64b6077e943458e27b8b5542dfded80e2f871fad.Validation
validation_only=true; it is not validation of the target-branch merge result.This PR only proposes branch synchronization. No automatic merge or label changes.