Added support for custom timestamp format #2614
jprakash-dbAnnotations
1 error and 1 warning
|
check
You have 2 commits 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 rebase HEAD~2 --signoff
```
Now your commits will have your sign off. Next run
```bash
git push --force-with-lease origin jprakash-db/custom-timestamp-format
```
Commit sha: [bf21af2](https://github.com/databricks/databricks-sql-python/pull/755/commits/bf21af22c250db84a114c007b19409d04257f1a4), Author: Jothi Prakash, Committer: Jothi Prakash; The sign-off is missing.
Commit sha: [e34f374](https://github.com/databricks/databricks-sql-python/pull/755/commits/e34f374bc15beaa33e85c782bcc86d2124a8814b), Author: Jothi Prakash, Committer: Jothi Prakash; The sign-off is missing.
|
|
check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7, tisonkun/actions-dco@v1.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|