Skip to content

Update incident comms workflow with private links and Google Sheet backup#15322

Open
inkeep[bot] wants to merge 1 commit intomasterfrom
docs-writer-ai-update-2026-02-26T09-53-18-766Z-4huxni
Open

Update incident comms workflow with private links and Google Sheet backup#15322
inkeep[bot] wants to merge 1 commit intomasterfrom
docs-writer-ai-update-2026-02-26T09-53-18-766Z-4huxni

Conversation

@inkeep
Copy link
Contributor

@inkeep inkeep bot commented Feb 26, 2026

Summary

This PR updates the incident communications workflow documentation to:

  1. Convert the insight link to a private link - The existing insight link for assessing customer impact is now wrapped with the <PrivateLink> component to indicate it's an internal resource
  2. Add a Google Sheet backup - Added a Google Sheet link as a backup resource, also wrapped with <PrivateLink>

Changes

Updated bullet point 3 in the Workflow section of the incident communications templates page:

Before:

Assess customer impact, this insight will help you understand...

After:

Assess customer impact, this insight (or this Google Sheet as a backup) will help you understand...

Both links are now marked as private internal resources using the <PrivateLink> component.


This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

@vercel
Copy link

vercel bot commented Feb 26, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
posthog Building Building Preview Feb 26, 2026 9:54am

Request Review

@github-actions
Copy link
Contributor

github-actions bot commented Feb 26, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Feb 26, 2026 10:00AM

@github-actions
Copy link
Contributor

Vale prose linter → found 12 errors, 14 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/handbook/growth/sales/communications-templates-incidents.md — 12 errors, 14 warnings, 0 suggestions
Line Severity Message Rule
7:64 warning Use the Oxford comma before 'and' or 'or' in a list of three or more items. PostHogBase.OxfordComma
9:156 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
13:119 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:34 warning Use the Oxford comma before 'and' or 'or' in a list of three or more items. PostHogBase.OxfordComma
37: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
38:160 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
50:104 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: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
54: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
57:17 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
77:5 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
83:10 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
94:6 warning 'Coordination within GTM' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
100:37 warning 'comms' is a possible misspelling. PostHogBase.Spelling
108:113 warning 'comms' is a possible misspelling. PostHogBase.Spelling
109:25 warning 'comms' is a possible misspelling. PostHogBase.Spelling
110:122 warning 'comms' is a possible misspelling. PostHogBase.Spelling
122:34 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
122: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
125:49 warning Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. PostHogBase.ProductNames
126:68 warning 'comms' is a possible misspelling. PostHogBase.Spelling
126:74 warning 'learnings' is a possible misspelling. PostHogBase.Spelling
130:43 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
131:42 warning 'comms' is a possible misspelling. PostHogBase.Spelling
137:4 warning 'Using Pylon for broadcasts' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
139:271 warning 'masse' is a possible misspelling. PostHogBase.Spelling

@inkeep
Copy link
Contributor Author

inkeep bot commented Feb 26, 2026

Thanks for the clarification on the <PrivateLink> formatting! I've reviewed the changes and confirmed that the syntax is already correct:

<PrivateLink url="https://us.posthog.com/project/2/insights/EBiXOD91">insight</PrivateLink>

and

<PrivateLink url="https://docs.google.com/spreadsheets/d/1EyV55L0vWTfD4W02j5A3Vx3YZYPUODmQQC1toFPcKXU/edit?gid=1396499197#gid=1396499197">Google Sheet</PrivateLink>

Both links follow the <PrivateLink url="url">text</PrivateLink> format as expected. Ready for review! 🚀

Copy link
Contributor

@ceyniustranberg ceyniustranberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant