This is an automated email from the ASF dual-hosted git repository.
yuchanns pushed a change to branch ci-bindings-go-behavior-tests
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard 89571c27a ci(bindings/go): remove behavior_test from ci lint
discard 56f838ee9 fix(bindings/go): cleanup
discard ab285aa51 fix(bindings/go): behavior test nested list
discard 3f0b8e835 ci(bindings/go): add script to generate scheme
discard 0b224e3d4 ci(bindings/go): include go into behavior tests
add 0da2ed451 docs(bindings/nodejs): fix broken links (#6017)
add d09d018b3 ci(bindings/go): include go into behavior tests
add a32379e43 ci(bindings/go): add script to generate scheme
add a939fb32d fix(bindings/go): behavior test nested list
add 49a3d9b56 fix(bindings/go): cleanup
add 2293b7055 ci(bindings/go): remove behavior_test from ci lint
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (89571c27a)
\
N -- N -- N refs/heads/ci-bindings-go-behavior-tests (2293b7055)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
bindings/nodejs/index.js | 4 +-
bindings/nodejs/package.json | 3 +-
bindings/nodejs/pnpm-lock.yaml | 240 +++++++++++++++++++++++-------------
bindings/nodejs/scripts/header.js | 8 +-
bindings/nodejs/theme/index.tsx | 39 +++---
bindings/nodejs/tsconfig.theme.json | 5 +-
bindings/nodejs/typedoc.json | 1 +
7 files changed, 179 insertions(+), 121 deletions(-)
