Skip to content

chore: add env variable to override repo name in case repo is published incorrectly #653

chore: add env variable to override repo name in case repo is published incorrectly

chore: add env variable to override repo name in case repo is published incorrectly #653

Triggered via pull request November 19, 2024 22:31
@sofislsofisl
synchronize #248
sofisl-patch-1
Status Failure
Total duration 1m 1s
Artifacts

ci.yaml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 1 warning
test (16): packages/server/src/lib/write-package.ts#L148
Replace `(repoName)` with `repoName`
test (16): packages/server/src/lib/write-package.ts#L149
Replace `(repo·as·{url:·string}).url·??·config.githubRepoName` with `⏎······(repo·as·{url:·string}).url·??·config.githubRepoName⏎····`
test (16)
Process completed with exit code 1.
test (14)
The job was canceled because "_16" failed.
test (14)
The operation was canceled.
test (12)
The job was canceled because "_16" failed.
test (12): packages/server/src/lib/write-package.ts#L148
Replace `(repoName)` with `repoName`
test (12): packages/server/src/lib/write-package.ts#L149
Replace `(repo·as·{url:·string}).url·??·config.githubRepoName` with `⏎······(repo·as·{url:·string}).url·??·config.githubRepoName⏎····`
test (12)
The operation was canceled.
test (16)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/