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.

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

Migrate to JavaScript action using Octokit for getting job_id/job_name #10

Open
Tiryoh opened this issue Feb 4, 2022 · 0 comments
Open

Comments

@Tiryoh
Copy link
Owner

Tiryoh commented Feb 4, 2022

First of all, thanks for pointing this out @IngoStrauch2020.

I have also come to the conclusion that it seems like quick fix of this problem is using per_page param of List jobs for a workflow run attempt to get the job lists, as you point out.

Also, after digging further, I found there are two ways to get the current job_id.

  1. Getting the current job_id directly

I haven't tested yet, but it seems like there are some ways to get the current job name using JavaScript actions.

actions/toolkit#550
actions/starter-workflows#292

  1. Using Octokit's pagination method to get all job name list

https://octokit.github.io/rest.js/v18#pagination
ref: https://maku.blog/p/7r6gr3d/ (written in Japanese)

I would like to support up to 100 jobs first, and then rewrite this action using Octokit.

Originally posted by @Tiryoh in #1 (comment)

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

No branches or pull requests

1 participant