Skip to content

[SPARK-35158][INFRA] Add guidance to retrigger forked workflow runs#55960

Closed
fallintoplace wants to merge 1 commit into
apache:masterfrom
fallintoplace:SPARK-35158-retrigger-workflow-guidance
Closed

[SPARK-35158][INFRA] Add guidance to retrigger forked workflow runs#55960
fallintoplace wants to merge 1 commit into
apache:masterfrom
fallintoplace:SPARK-35158-retrigger-workflow-guidance

Conversation

@fallintoplace
Copy link
Copy Markdown
Contributor

@fallintoplace fallintoplace commented May 18, 2026

What changes were proposed in this pull request?

This PR updates the Test results check summary in notify_test_workflow.yml to guide pull request authors on what to do after checking the forked workflow run.

Why are the changes needed?

SPARK-35158 notes that only pull request authors can rerun workflow runs in their forks. The check summary currently links to the test results, but does not tell authors to rerun unrelated failures or push follow-up changes for related failures.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Manually verified with:

ruby -ryaml -e 'YAML.load_file(".github/workflows/notify_test_workflow.yml"); puts "YAML OK"'
node --check <(ruby -ryaml -e 'script = YAML.load_file(".github/workflows/notify_test_workflow.yml").dig("jobs", "notify", "steps", 0, "with", "script"); puts "async function __check() {"; puts script; puts "}"')
git diff --check

Was this patch authored or co-authored using generative AI tooling?

Generated-by: GPT-5

@dongjoon-hyun
Copy link
Copy Markdown
Member

cc @HyukjinKwon who is the reporter of SPARK-35158 .

@fallintoplace fallintoplace force-pushed the SPARK-35158-retrigger-workflow-guidance branch from 13c4c5a to 436ecfa Compare May 18, 2026 21:31
@HyukjinKwon
Copy link
Copy Markdown
Member

Merged to master and branch-4.x.

HyukjinKwon pushed a commit that referenced this pull request May 18, 2026
### What changes were proposed in this pull request?

This PR updates the `Test results` check summary in `notify_test_workflow.yml` to guide pull request authors on what to do after checking the forked workflow run.

### Why are the changes needed?

SPARK-35158 notes that only pull request authors can rerun workflow runs in their forks. The check summary currently links to the test results, but does not tell authors to rerun unrelated failures or push follow-up changes for related failures.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Manually verified with:

```bash
ruby -ryaml -e 'YAML.load_file(".github/workflows/notify_test_workflow.yml"); puts "YAML OK"'
node --check <(ruby -ryaml -e 'script = YAML.load_file(".github/workflows/notify_test_workflow.yml").dig("jobs", "notify", "steps", 0, "with", "script"); puts "async function __check() {"; puts script; puts "}"')
git diff --check
```

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: GPT-5

Closes #55960 from fallintoplace/SPARK-35158-retrigger-workflow-guidance.

Authored-by: Minh Vu <vuhoangminh97@gmail.com>
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
(cherry picked from commit 1ad4fa4)
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants