Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Look into using runner.name as a optimization #6

Open
omus opened this issue Sep 20, 2024 · 0 comments
Open

Look into using runner.name as a optimization #6

omus opened this issue Sep 20, 2024 · 0 comments

Comments

@omus
Copy link
Member

omus commented Sep 20, 2024

In the future we may choose to use runner.name as a first pass in selecting the job from the GitHub API job list. I would consider this an optimization though as we would still need to the job name as either a fallback or as part of the selection criteria.

– #1 (comment)

See details on the context for runner.name which corresponds to the GitHub API job key job[*].runner_name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@omus