Add release announcement publishing skill#10371
Merged
jongalloway merged 3 commits intomainfrom Apr 14, 2026
Merged
Conversation
|
Azure Pipelines: 1 pipeline(s) require an authorized user to comment /azp run to run. |
|
Azure Pipelines: 1 pipeline(s) require an authorized user to comment /azp run to run. |
Member
Author
|
/azp run |
|
Azure Pipelines: 1 pipeline(s) were filtered out due to trigger conditions. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new repository skill that documents a safe, repeatable workflow for publishing .NET release discussions in dotnet/core and mirrored, locked announcement issues in dotnet/announcements, with an emphasis on avoiding duplicate creates and verifying results after write operations.
Changes:
- Introduces a new
.github/skills/publish-release-announcements/SKILL.mdskill describing preflight checks, creation, verification, and safe retry rules. - Documents duplicate-detection and “cancellation is ambiguous success” guidance to prevent double-posting.
- Provides concrete verification examples referencing a recent discussion and announcement issue.
Show a summary per file
| File | Description |
|---|---|
| .github/skills/publish-release-announcements/SKILL.md | New skill documenting the end-to-end publication workflow and safety/verification rules for release announcements. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 1
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Azure Pipelines: 1 pipeline(s) require an authorized user to comment /azp run to run. |
richlander
approved these changes
Apr 14, 2026
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
Add a new
publish-release-announcementsskill under.github/skills/to document the workflow for publishing .NET release discussions indotnet/coreand the locked mirror issues indotnet/announcements.What changed
Example references
Validation
npx markdownlint --config .github/linters/.markdown-lint.yml .github/skills/publish-release-announcements/SKILL.md