rapidsai / rapidsai/shared-actions
Telemetry: simplify GitHub job ID finding
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 15
- Avg merge
- 8h 7m
- Merged PRs (30d)
- 8
Description
The job ID (not to be confused with the higher-level run ID) has not been directly accessible in the past. Issue at https://github.com/orgs/community/discussions/8945
Github added support for the job ID here: https://github.blog/changelog/2025-09-18-actions-yaml-anchors-and-non-public-workflow-templates/#identify-running-jobs-with-job-check-run-id-in-github-actions-contexts
This can replace some hacky lookup stuff in shared-actions, like https://github.com/rapidsai/shared-actions/blob/457299ee7ea9886bd45978689edb2ca2bbfc6465/telemetry-impls/github-actions-job-info/action.yml#L68
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at shared-actions/telemetry-impls/github-actions-job-info/action.yml around line 68 and read the existing job ID lookup. Compare it with the GitHub Actions context support described in the linked changelog, then verify that telemetry still reports the correct job ID after the lookup is simplified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100