Release-testing: v8.5.6 tiflash repo CI trigger

[stevenayu]

Automated release-testing placeholder PR for pingcap/tiflash release-8.5.

This PR exists only to trigger CI FT via /test comments.
Do not merge.

Summary by CodeRabbit

• Chores
  • Added release testing configuration files to support CI/CD pipeline operations.

[ti-chi-bot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be LGTMed and approved by the reviewers firstly.
2. For pull requests to TiDB-x branches, it must have no failed tests.
3. AFTER it has lgtm and approved labels, please wait for the cherry-pick merging approval from triage owners.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jinhelin for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pingcap-cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A new markdown file was added to the .github/ directory containing a placeholder release configuration entry for TiFlash version 8.5.6, including repository details, target version, base release branch, and generated branch name.

Changes

Cohort / File(s)	Summary
Release Configuration .github/release-testing-ci-ft.md	Added placeholder release configuration entry with repository (pingcap/tiflash), target version (v8.5.6), base release (release-8.5), and generated branch metadata. Includes "do not merge" notice.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A config file hopped into view,
With branches and versions so true,
A placeholder rest, not merged—just yet!
Release notes pending, no worries as set! 📋✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description significantly deviates from the required template, missing critical sections like problem statement, changes explanation, checklist items, and release notes.	Add required sections from the template: What problem does this PR solve, What is changed and how it works, Check List (with test selections), and Release note sections.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly corresponds to the main change: adding a release-testing configuration file to trigger CI for tiflash v8.5.6.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

.github/release-testing-ci-ft.md (1)

8-8: Use an explicit timezone in generated_at.

2026-04-01 16:24:26 is ambiguous for automation/auditing. Prefer ISO-8601 UTC (for example: 2026-04-01T16:24:26Z).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/release-testing-ci-ft.md at line 8, The timestamp value for the YAML
key generated_at is ambiguous; replace the current value `2026-04-01 16:24:26`
with an explicit ISO‑8601 UTC timestamp (e.g. `2026-04-01T16:24:26Z`) so
automation/auditing consumers unambiguously know the timezone—update the
generated_at value accordingly.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/release-testing-ci-ft.md:
- Line 8: The timestamp value for the YAML key generated_at is ambiguous;
replace the current value `2026-04-01 16:24:26` with an explicit ISO‑8601 UTC
timestamp (e.g. `2026-04-01T16:24:26Z`) so automation/auditing consumers
unambiguously know the timezone—update the generated_at value accordingly.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: d8a7029c-76d6-458d-89d1-94c3cf7dac3c

📥 Commits

Reviewing files that changed from the base of the PR and between 836d94d and 43f223a.

📒 Files selected for processing (1)

• .github/release-testing-ci-ft.md

[stevenayu]

/test ?

[ti-chi-bot]

@stevenayu: The following commands are available to trigger required jobs:

/test pull-integration-test

/test pull-unit-test

Details

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[stevenayu]

/test pull-integration-test pull-unit-test