GH-50293: [CI] Run check-labels for all triggers to avoid cancelling further steps and add tag to set_enabled#50340
Conversation
…check-labels is cancelled
|
|
There was a problem hiding this comment.
Pull request overview
This PR updates several “extra” CI workflows to enable their runs for tag events and to adjust gating around the check-labels dependency.
Changes:
- Add
github.ref_type == 'tag'as an enabling condition for the “extra” workflows. - Add a job-level
if:guard on each workflow’scheck-enabledjob.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| .github/workflows/r_extra.yml | Extends enablement logic to tags; adds job-level gating for check-enabled. |
| .github/workflows/package_linux.yml | Extends enablement logic to tags; adds job-level gating for check-enabled. |
| .github/workflows/cuda_extra.yml | Extends enablement logic to tags; adds job-level gating for check-enabled. |
| .github/workflows/cpp_extra.yml | Extends enablement logic to tags; adds job-level gating for check-enabled. |
|
I've tested a couple of things on my fork. I've merged the commits on this branches individually and have created a tag on my fork to trigger the jobs. |
Rationale for this change
Currently when check-labels is not a pull_request even the following steps are cancelled. Also we don't enable tags execution which is required for releases.
What changes are included in this PR?
Run check-labels for the specified events and enable jobs for tags.
Are these changes tested?
I've tested on my fork by pushing to main and creating tags, more details on the comment on the PR.
Are there any user-facing changes?
No