Skip to content

Conversation

@Lotte-Verheyden
Copy link
Contributor

Update GitHub Actions integration documentation to include a webhook proxy workaround for repository_dispatch payload format incompatibility.

The original documentation implied a direct integration, but GitHub's repository_dispatch API requires event_type and client_payload fields, which Langfuse webhooks do not provide directly. This PR adds a necessary intermediate webhook proxy step with code examples (Cloudflare Workers, Python FastAPI) to transform the payload, resolving the issue where direct integration failed.


Linear Issue: LF-2078

Open in Cursor Open in Web

@cursor
Copy link

cursor bot commented Dec 4, 2025

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@vercel
Copy link

vercel bot commented Dec 4, 2025

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

Project Deployment Preview Comments Updated (UTC)
langfuse-docs Ready Ready Preview Comment Dec 4, 2025 11:19am

@github-actions
Copy link

github-actions bot commented Dec 4, 2025

📦 Next.js Bundle Analysis for langfuse-docs

This analysis was generated by the Next.js Bundle Analysis action. 🤖

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/docs/prompt-management/features/github-integration 64.44 KB 469.01 KB 134.00% (🟡 +0.67%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

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.

3 participants