Repository navigation
docs(release-skill): add feature walkthrough threads to the announcement style - #1091
Merged
AJ Alon (ajalon1) merged 2 commits intoNov 21, 2026
Conversation
…ent style Capture what worked for the v0.20.0 auth-profiles announcement in #dr-cli so the next headline feature can reuse it: - A "Feature walkthrough threads" section: show the plan and agree on use cases and example names first, one real-life use case per reply, correct an earlier announcement's claim in the thread, link demo docs by release tag, and keep internal hostnames out of examples. - Fold a patch release into the last reply of the release it follows when that release's announcement was deferred. - Posting mechanics for the Claude.ai Slack connector: standard markdown, a thread_ts taken from the main post, and replies sent one at a time to keep their order. - Verification: build the release tag and run quoted output against an offline scratch config, and test confirmations with and without --yes.
AJ Alon (ajalon1)
marked this pull request as ready for review
November 21, 2026 01:27
Co-authored-by: AJ Alon <aj.alon@datarobot.com>
Code OwnershipAgent Lifecycle
Review requested from the teams above. Labels will be removed automatically upon approval. |
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.
RATIONALE
The v0.20.0 auth-profiles announcement in #dr-cli used a longer format than the style guide described: a main post plus seven thread replies, one per real-life use case. This records what worked, so the next headline feature (or the next agent running the
releaseskill) can reuse it without rediscovering it.Thread: https://datarobot.slack.com/archives/C01F2KWLYBG/p1794549397954499
CHANGES
All changes are in
.factory/skills/release/references/announcement-style.md(also reachable through the.claude/skills/releasesymlink):slack_send_messagetakes standard markdown, replies needthread_tsfrom the main post, and replies go out one at a time to keep their order.--yes. That check found ALIFE-1473.TESTING
Docs-only change. Re-read the rendered markdown; no code or behavior changes.
RELATED
🤖 Generated with Claude Code