Automated QA metrics arrive in pull requests
Pull request reviewers now get automatic comparisons of memory heap usage against 14-day baselines, making performance changes visible before code gets merged.
Performance regressions are notoriously difficult to catch during code review—memory leaks and resource spikes often hide until production. Pull request reviewers previously had no standard way to see how a change might affect memory usage or build artifacts until after the code shipped.
This PR adds automated QA metrics reporting directly into the pull request workflow. When a PR triggers the E2E performance test job, a comment is posted or updated on the PR that compares key metrics—starting with memory heap usage—against a 14-day rolling baseline. Docker image sizes for the n8n and runners images are also tracked.
The system works by fetching metric data from an external webhook, then posting a markdown comparison to the PR via the GitHub API. Comments are idempotent—the script finds and updates an existing comment rather than flooding the PR with new ones.
In the n8n project codebase, this gives every reviewer immediate insight into whether a change meaningfully impacts memory consumption or build size, without needing to run performance tests locally or dig through CI logs.
View Original GitHub Description
Summary
Introduces a GitHub Actions job for E2E performance tests and a script to fetch their results.
Posts or updates a comment on pull requests with a comparison of key QA metrics, starting with memory heap usage baseline. This provides early visibility into performance changes directly within the PR review process.
Related Linear tickets, Github issues, and Community forum posts
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)