Skip to content

chore(desktop): rename inbox signal source group to "External sources" - #76579

Draft
joshsny wants to merge 1 commit into
masterfrom
posthog-code/rename-external-sources-label
Draft

chore(desktop): rename inbox signal source group to "External sources"#76579
joshsny wants to merge 1 commit into
masterfrom
posthog-code/rename-external-sources-label

Conversation

@joshsny

@joshsny joshsny commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Problem

The inbox signal-sources section groups external integrations under a header that does not match its counterpart in the main PostHog app ("Connected tools" there, "External connections" here). The naming should be consistent across both surfaces.

This is a port of PostHog/code#3967, which was approved and green but can never merge: PostHog/code is now frozen behind a "block all PRs" ruleset after the monorepo migration, so the ref cannot be updated there.

Changes

Renames the signal-sources group header (and its loading skeleton) from External connections to External sources, matching the sibling "PostHog data" group.

How did you test this code?

I (actually the PostHog Slack agent) did not run the app or any tests for this. It is a two-string copy change in one component, ported byte-for-byte from the already-approved and fully-green PostHog/code#3967, and I verified by grep that the live header and the skeleton header are the only occurrences.

Automatic notifications

  • Publish to changelog?
  • Alert Sales and Marketing teams?

🤖 Agent context

Human-driven (agent-assisted). Ported by the PostHog Slack agent at the request of the original PR's author, who is assigned as DRI.


Created with PostHog from a Slack thread

Matches the "Connected tools"/"External sources" naming used in the main app so the inbox signal-sources section is consistent across surfaces. Label-only change, no behavior change.

Generated-By: PostHog Code
Task-Id: 40710cb7-2e49-43a6-b7a9-2812ca5250ae
@joshsny joshsny self-assigned this Aug 3, 2026
@trunk-io

trunk-io Bot commented Aug 3, 2026

Copy link
Copy Markdown

Merging to master in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Hey @joshsny! 👋

It looks like your git author email on this PR isn't your @posthog.com address (joshua@timenavi.com). Since you're on the PostHog team, it's worth pointing your local git author email at your @posthog.com address. Why it matters:

  • Consistent work identity in git history — internal tooling that attributes commits to team members keys off your @posthog.com address.
  • Keeps team contributions easy to tell apart from external community ones when scanning history.

You can fix it for this repo with:

git config user.email "you@posthog.com"

Or set it globally with git config --global user.email "you@posthog.com". No need to redo this PR — just a nudge for next time. 🙂

@github-actions github-actions Bot added the feature/desktop Feature Tag: Desktop label Aug 3, 2026
@trunk-io

trunk-io Bot commented Aug 3, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

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

Labels

feature/desktop Feature Tag: Desktop

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant