Skip to content

fix(SUPP-148): Fix broken Event Approval link in Data Clean-Up - #11

Merged
myronkaifung merged 3 commits into
mainfrom
copilot/supp-148-fix-broken-hyperlink
Jun 9, 2026
Merged

fix(SUPP-148): Fix broken Event Approval link in Data Clean-Up#11
myronkaifung merged 3 commits into
mainfrom
copilot/supp-148-fix-broken-hyperlink

Conversation

Copilot AI commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

The "Event Approval" link in the Other resources section of the Data Clean-Up page pointed to a changelog entry (/changelogs/2023-06-01-event-approval) that returns 404.

Changes

  • docs/data-governance/data-clean-up.mdx — Updated broken link to point to the correct documentation page:
    - - [Event Approval](/changelogs/2023-06-01-event-approval)
    + - [Event Approval](/docs/data-governance/event-approval)
Original prompt
<title>Bug: Broken Hyperlink in Data Clean-Up</title> **Type:** Bug · **Fix before launch:** Yes · **Reporter:** Cara Cheng

Bug summary
Event Approval hyperlinks to a 404 changelog.

URL
https://mixpanel-edb78807.mintlify.app/docs/data-governance/data-clean-up#other-resources

Screenshots/videos
1 image in the source Notion entry — see link below.


Migrated from Notion · source entry


Fix before launch

Only assign incident/ labels when asked to by a user. incident/ labels are reserved for customer facing incidents.
Fixes https://linear.app/mixpanel/issue/SUPP-148/bug-broken-hyperlink-in-data-clean-up

Branch naming

This task relates to issue SUPP-148 — preserve that identifier somewhere in the branch name and pull request title for traceability. Do not treat the identifier as a verbatim slug or prepend it with a hyphen by default; instead, adapt the full branch name to comply with the repository's branch-naming pattern, adding any required prefix or restructuring the shape as needed.

Include a link to the original issue in the pull request description: https://linear.app/mixpanel/issue/SUPP-148/bug-broken-hyperlink-in-data-clean-up

@linear-code

linear-code Bot commented Jun 9, 2026

Copy link
Copy Markdown
SUPP-148 Bug: Broken Hyperlink in Data Clean-Up

Type: Bug · Fix before launch: Yes · Reporter: Cara Cheng

Bug summary
Event Approval hyperlinks to a 404 changelog.

URL
https://mixpanel-edb78807.mintlify.app/docs/data-governance/data-clean-up#other-resources

Screenshots/videos
1 image in the source Notion entry — see link below.


Migrated from Notion · source entry

Review in Linear · Agent session

Copilot AI changed the title [WIP] Fix broken hyperlink in data clean-up Jun 9, 2026
Copilot AI requested a review from myronkaifung June 9, 2026 21:28
@greptile-apps

greptile-apps Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 5/5

Safe to merge — single-line docs link fix targeting a confirmed existing page.

The change replaces a dead changelog URL with a valid docs path that resolves to an existing file (event-approval.mdx). No logic, configuration, or user-facing behavior is affected beyond the corrected hyperlink.

No files require special attention.

Important Files Changed

Filename Overview
docs/data-governance/data-clean-up.mdx Single-line fix replacing a broken changelog link with the correct docs page for Event Approval, which exists at the new path.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Data Clean-Up page\n/docs/data-governance/data-clean-up"] -->|"Other Resources link (before)"| B["❌ 404\n/changelogs/2023-06-01-event-approval"]
    A -->|"Other Resources link (after)"| C["✅ Event Approval docs\n/docs/data-governance/event-approval"]
Loading

Reviews (2): Last reviewed commit: "Merge branch 'main' into copilot/supp-14..." | Re-trigger Greptile

@myronkaifung
myronkaifung marked this pull request as ready for review June 9, 2026 21:29
@myronkaifung
myronkaifung requested a review from a team as a code owner June 9, 2026 21:29
@myronkaifung
myronkaifung requested review from Tofufu and myronkaifung and removed request for a team and Tofufu June 9, 2026 21:29
@myronkaifung
myronkaifung enabled auto-merge (squash) June 9, 2026 21:30
@myronkaifung
myronkaifung disabled auto-merge June 9, 2026 21:45
@myronkaifung
myronkaifung merged commit 64e3110 into main Jun 9, 2026
7 checks passed
@myronkaifung
myronkaifung deleted the copilot/supp-148-fix-broken-hyperlink branch June 9, 2026 21:50
tylergoerzen-mxp added a commit that referenced this pull request Aug 20, 2026
Completes rec #20 Part B's gate list.

- New check_openapi.py: parses all 14 specs, requires openapi/info/paths,
  and resolves every local $ref. Uses openapi-spec-validator for full
  schema validation when installed, and still runs structurally without
  it. Passes on all 14 specs today; rejects a spec with a dangling $ref.
- check_frontmatter.py now requires a non-empty description and fails on
  duplicate rendered titles, which rec #11 asked for.
- Pin actions/checkout and actions/setup-python to commit SHAs, matching
  stale.yml. Collapse four near-identical jobs into one with ordered
  steps, and add a concurrency group.

MERGE ORDER: the frontmatter gate is red until #172 (description
backfill) and #178 (title dedupe) land. Verified against the #172 tree:
all description errors clear, leaving only the duplicate titles that
#178 resolves. Merge this last, as the plan intends.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
tylergoerzen-mxp added a commit that referenced this pull request Aug 20, 2026
Rec #11 asks for a CI uniqueness test on rendered titles, which only
passes at zero duplicates. Three pairs survived the first pass:

- Data Pipeline Integrations: the old-pipelines copy is now marked
  (Legacy), keeping "Integrations" as its sidebar label
- Lookup Tables: the reference page is the API, so it becomes
  Lookup Tables API
- Mixpanel Headless: the guide gets the benefit-style title, leaving the
  bare product name to the docs page

Verified zero duplicate titles across the tree, so the frontmatter gate
in #180 can enforce uniqueness once this and #172 land.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants