Skip to content

stability-test-release-8.5-non-next-gen - 2026-03-28 18:03:40 #4629

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hongyunyan wants to merge 1 commit into from
Closed

stability-test-release-8.5-non-next-gen - 2026-03-28 18:03:40 #4629

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -342,3 +342,4 @@ workload: tools/bin/workload

generate-next-gen-grafana:
./scripts/generate-next-gen-metrics.sh

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Mar 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This automated PR for stability testing modifies the Makefile solely to trigger a CI pipeline. This practice adds noise to the commit history of a core file, making it harder to track meaningful changes over time.

A better practice is to use a dedicated file for this purpose, for instance, ci/stability-trigger.txt. The automation can then modify this file to create a diff, keeping the history of important files like Makefile clean.

Loading