Skip to content

fix: event start behavior from the pipeline jobs view#1575

Merged
minghay merged 1 commit into
masterfrom
start-job-table
May 16, 2026
Merged

fix: event start behavior from the pipeline jobs view#1575
minghay merged 1 commit into
masterfrom
start-job-table

Conversation

@yk634
Copy link
Copy Markdown
Contributor

@yk634 yk634 commented May 15, 2026

Context

In the pipeline jobs job list view, the start action was using the SHA from the latest pipeline event instead of the repository's latest commit.

This area had also become harder to follow because the same confirm-action flow is used from both pipeline/jobs and pipeline/workflow, and the branching logic had grown to cover multiple cases in one place.

In addition, the jobs view modal state was not being reset correctly. After opening the restart modal and closing it, a subsequent start action could incorrectly reuse restart-related event data.

Objective

Update the pipeline jobs job list view so that the start action uses the repository's latest commit instead of the latest pipeline event SHA.

This PR also:

  • refactors the confirm-action branching to make the different jobs view and workflow cases clearer
  • fixes stale modal state in the jobs view so restart event data is not carried into a later start action

References

License

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@minghay minghay merged commit afe36e2 into master May 16, 2026
2 checks passed
@minghay minghay deleted the start-job-table branch May 16, 2026 01:52
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