Skip to content

specifying the branch name when cloning a repository #15

specifying the branch name when cloning a repository

specifying the branch name when cloning a repository #15

Triggered via push February 4, 2024 21:57
Status Success
Total duration 2m 28s
Artifacts

build.yaml

on: push
Build binaries and link them to the release
2m 19s
Build binaries and link them to the release
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build binaries and link them to the release
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-go@v3, goreleaser/goreleaser-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build binaries and link them to the release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, goreleaser/goreleaser-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build binaries and link them to the release
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/
Build binaries and link them to the release
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/