Repository navigation
feat(error-tracking): add release-linking fixtures for Python, Ruby and PHP - #4266
Merged
Merged
Conversation
…nd PHP Three error-tracking apps with production deploy pipelines, one per language: - cicd-github-actions-docker-python-flask: Flask, GitHub Actions, Docker image rolled out over SSH with docker run - cicd-gitlab-ruby-sinatra: Sinatra on an older posthog-ruby, GitLab CI deploy over SSH to a systemd unit with an EnvironmentFile - cicd-github-actions-docker-php-laravel: Laravel on php-fpm with clear_env, config:cache at start, compose rollout over SSH The expectations live in apps/error-tracking/README.md, outside the app directories the wizard agent reads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 29, 2026
ablaszkiewicz
marked this pull request as ready for review
September 30, 2026 10:42
hpouillot
approved these changes
Sep 30, 2026
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
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.
Pull requests — release linking for Python, Ruby and PHP spans three repos:
error-tracking-link-releasesskill and thelink-releasesflow taskProblem
The error-tracking fixtures cover source-map upload only. Python, Ruby and PHP apps now get release linking in the production deploy (PostHog/context-mill#416), which needs apps with real deploy pipelines to run against.
Changes
Three apps under
apps/error-tracking/, one per language, each with a different deploy path:cicd-github-actions-docker-python-flaskdocker runover SSH;ci.ymltests pull requestscicd-gitlab-ruby-sinatraposthog-ruby3.20.0deployjob onruby:3.3-slimSSHes in and restarts a systemd unit with anEnvironmentFile; thetestjob covers merge requestscicd-github-actions-docker-php-laravelphp:8.4-fpm-alpine, no PostHogconfig:cacheand the pool setsclear_env = yesapps/error-tracking/README.md. The app READMEs describe only the project, because the agent reads them and would take expectations as instructions.storage/**/.gitignoreandbootstrap/cache/.gitignoreplaceholders, force-added past the root**/storage/rule, so a clean checkout builds and boots.bin/dev, because the root.gitignoreexcludesMakefile.How it was tested
Headless
wizard error-tracking --ci --local-context-millruns against copies of each app, followed by runtime checks that deploy the result the way its pipeline does. All three pass; the results table is in PostHog/context-mill#416. The Laravel app also builds and boots from a cleangit archiveof this branch.🤖 Generated with Claude Code