Repository navigation
Require placeholder confirmation before release announcements - #1039
Merged
Guanzhou Song (guanzhousongmicrosoft) merged 3 commits intoOct 21, 2026
Merged
Guanzhou Song (guanzhousongmicrosoft) merged 3 commits into
Guanzhou Song (guanzhousongmicrosoft) merged 3 commits into
Conversation
Ask whether a release discussion placeholder exists before publishing, and reuse a confirmed placeholder instead of creating a duplicate. Preserve version-based parent lookup and publish-before-comment ordering for patch announcements. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
✅ CI passed: standard tier (ready PR)Commit
Full run: add the Code quality
Build sizeNo page, activation, VSIX or other bundle size changed by 5% or 50 KiB or more against Artifacts: VSIX | Bundle-reports-39642707125 | L1-manifest-report-39642707125 All graphs (exact bytes)
Packaged bytes. Shared chunks count in every graph that loads them, so rows do not add up. Updated in place on every run. |
Apply the repository formatter to the placeholder-reuse documentation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Tomasz Naumowicz (tnaum-ms)
marked this pull request as ready for review
October 20, 2026 11:08
Tomasz Naumowicz (tnaum-ms)
requested a review
from Guanzhou Song (guanzhousongmicrosoft)
October 20, 2026 11:09
Guanzhou Song (guanzhousongmicrosoft)
approved these changes
Oct 21, 2026
Guanzhou Song (guanzhousongmicrosoft)
enabled auto-merge
October 21, 2026 17:19
Guanzhou Song (guanzhousongmicrosoft)
deleted the
dev/tnaum/release-notes-skill-update
branch
October 21, 2026 17:24
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
Require the release-notes agent to ask whether a placeholder discussion already exists before publishing a release announcement, so an existing WIP announcement is reused instead of duplicated.
Scope
Documentation and agent workflow only. The branch was fast-forwarded to current
mainbefore applying this focused change. The older, uncommitted publishing draft was preserved in a local stash rather than reintroduced alongside the current guide.No changes to notification behavior, image uploads, release contents, or dependency manifests. No release announcement was published while validating this change.
Validation
Case 2 checks ran after the request to mark this PR ready:
npm run prettier-fixpassed; its formatting changes were committed and pushed.npm run lintpassed.npm run buildpassed, including workspace builds.npm run packagepassed.git diff --checkpassed.Review readiness
This PR remains a draft because the required AI pre-review and recorded author decisions have not been committed. The automated handoff checks passed, but that review requirement is still outstanding.