This is an automated email from the ASF dual-hosted git repository.
EnxDev pushed a change to branch enxdev/feat/chatbot-permissions
in repository https://gitbox.apache.org/repos/asf/superset.git
discard c47fb16ebe3 feat(extensions): backend settings persistence and
admin-only permissions
discard d3d39e06d73 feat(extensions): admin configuration UI for extensions
discard d195371ef73 feat(extensions): eager-load extensions at app-shell
startup
discard e2e679ae23e feat(extensions): define the chatbot entry point in the
frontend API
discard c5e0696ab9e feat(extensions): define the superset.chatbot contribution
point
add c77c9b29f96 feat(extensions): define the superset.chatbot contribution
point
add 5e98ff968df feat(extensions): define the chatbot entry point in the
frontend API
add 1bf86dfd8f2 feat(extensions): eager-load extensions at app-shell
startup
add 8d8a4dbf065 feat(extensions): admin configuration UI for extensions
add 6bd550e5022 feat(extensions): backend settings persistence and
admin-only permissions
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 (c47fb16ebe3)
\
N -- N -- N refs/heads/enxdev/feat/chatbot-permissions
(6bd550e5022)
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:
.../superset-core/src/contributions/index.ts | 47 ++++++++++++++++++++++
.../packages/superset-core/src/views/index.ts | 22 +++++++---
2 files changed, 63 insertions(+), 6 deletions(-)
