docs: add #changelog and #coming-soon Slack channel guidance to handbook#17098
Merged
joethreepwood merged 1 commit intoMay 29, 2026
Merged
Conversation
Documents the #changelog (just shipped, Docs & Wizard, real-time) and #coming-soon (shipping soon, Marketing, daily digest) Slack channels across the handbook. Explains the underlying agentic workflows that scan PRs and feature flag changes, the manual opt-in via PR template checkboxes and the @PostHog Slack app, and recommends everyone joins. The changelog publishing page is the canonical reference; the other pages link back to it with a short, audience-appropriate summary. Generated-By: PostHog Code Task-Id: b76f4a31-def9-4a20-ab3e-f86ce85f99e5
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 49 errors, 61 warnings, 1 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 22:381 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 24:53 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 24:185 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 32:1 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 33:1 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 34:1 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 44:77 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 72:166 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 110:249 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 126:35 | warning | Use 'GitHub' instead of 'Github'. | Vale.Terms |
| 134:15 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 134:117 | warning | Use 'GitHub' instead of 'Github'. | Vale.Terms |
| 134:147 | warning | Use 'GitHub' instead of 'github'. | Vale.Terms |
| 134:158 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 143:9 | warning | Use 'URL' instead of 'url'. | Vale.Terms |
| 153:493 | warning | 'searchability' is a possible misspelling. | PostHogBase.Spelling |
| 157:4 | warning | 'Slackbot' is a possible misspelling. | PostHogBase.Spelling |
| 157:229 | warning | 'Slackbot' is a possible misspelling. | PostHogBase.Spelling |
| 163:66 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 164:68 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 166:38 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 177:98 | warning | 'eg' is a possible misspelling. | PostHogBase.Spelling |
| 177:160 | warning | 'colleauge' is a possible misspelling. | PostHogBase.Spelling |
| 181:24 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 182:30 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 183:31 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 184:26 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 185:30 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 186:45 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 187:54 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 188:26 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 189:36 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 191:79 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 191:110 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 193:5 | warning | 'Google Docs and Slides' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 201:322 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 215:82 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 221:110 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 223:4 | warning | 'Requests for comment (RFCs)' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 235:244 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 235:316 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 239:5 | warning | 'When does it work best to write an RFC?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 250:5 | warning | 'When does a meeting / another approach work better than an RFC?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 254:43 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 256:5 | warning | 'How should I use AI when writing RFCs?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 262:5 | warning | 'Top tips for RFCs' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 265:54 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 267:174 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 271:119 | warning | 'websockets' is a possible misspelling. | PostHogBase.Spelling |
| 277:149 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 283:195 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 284:164 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 290:87 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 297:49 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 299:5 | warning | 'Google Calendar' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 301:91 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 308:5 | warning | 'Calendly' is a possible misspelling. | PostHogBase.Spelling |
| 310:8 | warning | 'Calendly' is a possible misspelling. | PostHogBase.Spelling |
| 312:4 | warning | 'Communication Methods' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 316:57 | warning | 'untrusted' is a possible misspelling. | PostHogBase.Spelling |
contents/handbook/docs-and-wizard/how-to-publish-changelog.mdx — 2 errors, 10 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 21:38 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 25:30 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 26:28 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 26:77 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 59:44 | warning | 'Strapi' is a possible misspelling. | PostHogBase.Spelling |
| 59:59 | warning | 'mainatined' is a possible misspelling. | PostHogBase.Spelling |
| 80:10 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 100:30 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 121:92 | warning | 'gifs' is a possible misspelling. | PostHogBase.Spelling |
| 145:23 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 145:31 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 149:29 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
contents/handbook/engineering/customer-comms.md — 3 errors, 5 warnings, 1 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 2:17 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 7:56 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 7:159 | suggestion | Prefer 'proper nouns or they' over 'He'. | PostHogBase.Inclusivity |
| 7:176 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 16:110 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 16:261 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 20:37 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 20:83 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 25:40 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
contents/handbook/growth/sales/overview.md — 10 errors, 3 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 7:178 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 13:20 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 15:7 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 17:29 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 19:40 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 23:51 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 34:248 | error | 'win' is repeated! | Vale.Repetition |
| 46:138 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 52:167 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 72:4 | warning | 'Who the Sales team are' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 80:40 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 84:154 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 89:40 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
contents/handbook/marketing/index.md — 0 errors, 15 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 12:46 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 13:76 | warning | 'Influencers' is a possible misspelling. | PostHogBase.Spelling |
| 27:40 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 37:46 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 37:149 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 65:19 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 71:99 | warning | 'clickbaity' is a possible misspelling. | PostHogBase.Spelling |
| 101:66 | warning | 'Combinator' is a possible misspelling. | PostHogBase.Spelling |
| 107:184 | warning | 'superfans' is a possible misspelling. | PostHogBase.Spelling |
| 115:15 | warning | 'influencers' is a possible misspelling. | PostHogBase.Spelling |
| 115:72 | warning | 'influencers' is a possible misspelling. | PostHogBase.Spelling |
| 115:90 | warning | 'Theo' is a possible misspelling. | PostHogBase.Spelling |
| 115:99 | warning | 'Fireship' is a possible misspelling. | PostHogBase.Spelling |
| 123:143 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 129:134 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
contents/handbook/support/support-team.md — 1 errors, 1 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 26:145 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 31:40 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
74 tasks
gewenyu99
approved these changes
May 28, 2026
Contributor
gewenyu99
left a comment
gewenyu99
left a comment
There was a problem hiding this comment.
Makes sense.
Now just to be annoying:
- Is everything in #coming-soon going to end up in the changelog eventually?
- Should we actually use checkboxes for coming soon, or should every PR that's destined for the changelog, just appear in coming soon? We can look for open, unmerged PRs. Once they merge they end up in #changelog
Contributor
Author
|
I imagine they will appear in both, but it's possible they wouldn't.
For example if we had a security issue or a sensitive incident then it may
need a marketing/sales notification but wouldn't want to be in a changelog.
…On Thu, 28 May 2026, 22:13 Vincent (Wen Yu) Ge, ***@***.***> wrote:
***@***.**** approved this pull request.
Makes sense.
Now just to be annoying:
1. Is everything in #coming-soon going to end up in the changelog
eventually?
2. Should we actually use checkboxes for coming soon, or should every
PR that's destined for the changelog, just appear in coming soon? We can
look for open, unmerged PRs. Once they merge they end up in #changelog
—
Reply to this email directly, view it on GitHub
<#17098?email_source=notifications&email_token=AUA6UKKZ5W5PLNUR4FCFOH345CTYJA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIMZYGQ4DEOBZHEY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#pullrequestreview-4384828991>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUA6UKKAONK4OMIX6DWUZ6D45CTYJAVCNFSM6AAAAACZRHZXLOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHM2DGOBUHAZDQOJZGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Contributor
|
Great, as long as there's a reason for both sgtm |
joethreepwood
deleted the
posthog-code/handbook-changelog-coming-soon-channels
branch
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
3 participants
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.
Changes
Adds guidance to the handbook explaining the two internal Slack channels that surface what we ship:
#changelog— what's just shipped. Owned by the Docs & Wizard team. Updates constantly as PRs merge.#coming-soon— what's shipping soon. Owned by the Marketing team. Posts a daily digest.Both channels are powered by agentic workflows that scan merged PRs and feature flag changes in
posthog/posthog, classify them, and summarize them into the relevant channel. PR authors can opt in or out manually via the Publish to changelog? and Alert Sales and Marketing teams? checkboxes on theposthog/posthogPR template, or via the@posthogSlack app.how-to-publish-changelogis the canonical reference; the other pages add a short, audience-appropriate summary and link back.Pages updated:
contents/handbook/company/communication.md— under the Slack sectioncontents/handbook/docs-and-wizard/how-to-publish-changelog.mdx— canonical reference, expanded with the#coming-soonchannel and manual opt-in mechanismscontents/handbook/engineering/customer-comms.mdcontents/handbook/growth/sales/overview.mdcontents/handbook/marketing/index.mdcontents/handbook/support/support-team.mdChecklist
Created with PostHog Code