ci: match all nextgen release branches in GitHub Actions

[wuhuizuo]

What problem does this PR solve?

Issue Number: Ref #10560

What is changed and how does it work?

ci(actions): match all nextgen release branches

Replace the hardcoded release-nextgen-20250815 workflow filter with release-nextgen-* in:

• .github/workflows/pd-tests.yaml
• .github/workflows/tso-function-test.yaml

This keeps the existing non-nextgen branch coverage unchanged while allowing future nextgen release branches to trigger the same GitHub Actions workflows.

Check List

Tests

• Manual test (add detailed scripts or steps below)
  • git diff --check
  • verified only the two workflow branch filters changed
  • confirmed the nextgen workflow branch filters now use release-nextgen-*

Code changes

• Has the configuration change

Related changes

• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

Hi @wuhuizuo. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated two GitHub Actions workflows to broaden branch triggers: replaced release-nextgen-20250815 with the wildcard release-nextgen-* for both push and pull_request events in .github/workflows/pd-tests.yaml and .github/workflows/tso-function-test.yaml.

Changes

Cohort / File(s)	Summary
GitHub Workflow Branch Trigger Updates /.github/workflows/pd-tests.yaml, /.github/workflows/tso-function-test.yaml	Replaced the specific branch release-nextgen-20250815 with the wildcard pattern release-nextgen-* in both push.branches and pull_request.branches triggers to expand workflow activation to all nextgen release branches.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Track GitHub Actions support for release-nextgen-* branches #10558 — Same change pattern: replacing release-nextgen-20250815 with release-nextgen-* in workflow branch filters; likely the same intent.

Poem

🐰 I hopped through branches, wild and free,
Replaced one name with a shining -,
Now workflows dance on every spring,
Fluffy commits and CI sing,
🥕✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is mostly complete with problem statement, changes explanation, and a checklist. However, a critical required section is missing.	Add a GitHub issue link in the 'What problem does this PR solve?' section. The template requires 'Issue Number: Close #xxx' format to properly link and track the issue.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: replacing hardcoded nextgen release branch patterns with wildcards in GitHub Actions workflows.
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.}

[wuhuizuo]

/retest

[ti-chi-bot]

@wuhuizuo: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.95%. Comparing base (319d880) to head (6ad14de).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10549   +/-   ##
=======================================
  Coverage   78.95%   78.95%           
=======================================
  Files         532      532           
  Lines       71862    71862           
=======================================
  Hits        56741    56741           
- Misses      11094    11095    +1     
+ Partials     4027     4026    -1     

Flag	Coverage Δ
unittests	78.95% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[wuhuizuo]

/check-issue-triage-complete

[okJiang]

/ok-to-test

[bufferflies]

repeat #10550

[wuhuizuo]

repeat #10550

@bufferflies #10550 is expected to merge into nextgen release branch

this one is to avoid to create pull request every time when new nextgen release created.

[wuhuizuo]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: okJiang, rleungx

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [okJiang,rleungx]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-04-07 02:41:25.495002393 +0000 UTC m=+837690.700362450: ☑️ agreed by rleungx.
• 2026-04-08 07:38:42.713075429 +0000 UTC m=+941927.918435486: ☑️ agreed by okJiang.

[rleungx]

/retest

[ti-chi-bot]

@wuhuizuo: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-unit-test-next-gen-2	6ad14de	link	unknown	/test pull-unit-test-next-gen-2

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.