Synchronize a canceled workflow in the run list

User intention

Cancel a waiting workflow run.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both
BeforeThe defect at the parent commit
0:00.00 / 0:00.00Frame 0 · Hover the Build checks run's status icon in the Actions list.

Cancel the waiting workflow, inspect the returned list, and compare it with a diagnostic manual refresh.

AfterThe same script once the merged fix is applied
0:00.00 / 0:00.00Frame 0 · Hover the Build checks run's status icon in the Actions list.

Cancel the waiting workflow, return to the Actions list, and inspect the run status.

How is it judged?

01 · Given
Restore the data and starting state.
A signed-in user is on the repository's Actions list. Build checks #1 (Add project build checks) is Waiting, and the repository has no online runner.

02 · When
Perform the interaction.
Open the waiting run, click Cancel workflow run, verify that its detail shows Canceled, then use browser Back to return to the retained Actions list and observe its status without manually refreshing.

03 · Judge
Rationale: The run detail and Actions list describe the same workflow. A list that still says Waiting after cancellation gives contradictory status and makes the user refresh to establish what happened.
Require
On returning to the Actions list, reflect the canceled run automatically on reentry or within a reasonable synchronization interval, without manual refresh. Keep its identity and list context understandable.
Allowed
  • Refresh on reentry, periodic updates, or server-driven updates are acceptable; no specific polling algorithm is required.
  • Status wording, icons, and layout may vary if the canceled state is unambiguous.
  • Cancellation may end a waiting run without any runner ever executing it.

Who repaired it

More from Gitea

Self-hosted Git forge with issues, CI and packages

Explain Actions secret naming rules after the reference repair
Developer tools
Explain Actions secret naming rules
Native HTML5 validation blocks submission, focuses Name, and says Please match the requested format. The dialog retains the entered values but does not explain that the initial digit is invalid or how to correct it.
#39221
Preserve selections when batch closing issues fails after the reference repair
Developer tools
Preserve selections when batch closing issues fails
The native request fails with HTTP 412. The interface shows no error message, reloads the list, clears both selections, and restores the filter toolbar. All three issues remain open (3 Open, 0 Closed). A browser-console error is not feedback visible to the person using the list.
#38593
Use local tabs in the branch selector after the reference repair
Developer tools
Use local tabs in the branch selector
The tab adopts link-like hover styling. Clicking keeps the same Code page, dropdown, active Branches tab, and main branch content; the retained Reproduction issue context additionally reports an added trailing # and focus on Filter branch. The unchanged active-tab content is normal; the misleading link semantics and empty-fragment navigation side effect are the defect. Browser chrome is not present in the replay video, so the URL observation relies on the retained Reproduction context, not visual confirmation in the video.
#39285