Skip to content

[PECO-2050] Add custom auth headers into cloud fetch request #444

[PECO-2050] Add custom auth headers into cloud fetch request

[PECO-2050] Add custom auth headers into cloud fetch request #444

Triggered via pull request October 25, 2024 00:01
Status Failure
Total duration 11s
Artifacts

dco-check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
check
Unhandled error: HttpError: Resource not accessible by integration
check
You only have one commit incorrectly signed off! To fix, first ensure you have a local copy of your branch by [checking out the pull request locally via command line](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally). Next, head to your local branch and run: ```bash git commit --amend --no-edit --signoff ``` Now your commits will have your sign off. Next run ```bash git push --force-with-lease origin PECO-2050 ``` Commit sha: [b6b93b5](https://github.com/databricks/databricks-sql-go/pull/249/commits/b6b93b5ecd9b060f43e6aa397582b724fec6fa75), Author: Jacky Hu, Committer: Jacky Hu; The sign-off is missing.
check
The following actions uses node12 which is deprecated and will be forced to run on node16: tisonkun/actions-dco@v1.1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check
The following actions use a deprecated Node.js version and will be forced to run on node20: tisonkun/actions-dco@v1.1, actions/github-script@v6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/