Skip to content
Copy feature issue

[Schema Inaccuracy] Should GET /user/repos be paginated? #21

Sign in to view logs

[Schema Inaccuracy] Should GET /user/repos be paginated?

[Schema Inaccuracy] Should GET /user/repos be paginated? #21

Triggered via issue October 7, 2024 19:23
@beccobecco
labeled #4048 bdf624d
Status Success
Total duration 18s
Artifacts –

copy-feature-issue.yml

on: issues
Copy issue
8s
Copy issue
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Copy issue
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Copy issue
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Copy issue
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/