You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "sadpandajoe (via GitHub)" <gi...@apache.org> on 2026/08/06 17:57:26 UTC
[PR] fix(dashboard): redirect using sanitized slug from save response [superset]
sadpandajoe opened a new pull request, #42853:
URL: https://github.com/apache/superset/pull/42853
### SUMMARY
Fixes a dashboard post-save redirect bug (Shortcut sc-107323): when the **URL Slug** in *Edit dashboard properties* starts with a reserved URL character (`?` or `/`), saving succeeds but the post-save redirect lands on a malformed/blank URL on the **first** render. A manual page reload afterwards works, because the reload uses the stored, backend-sanitized slug.
**Root cause.** In `superset-frontend/src/dashboard/actions/dashboardState.ts`, the `onUpdateSuccess` handler in `saveDashboardRequest` built the redirect from the **raw, locally-submitted** slug:
```ts
navigateWithState(`/dashboard/${slug || id}/`, { event: 'dashboard_properties_changed' });
```
The backend sanitizes reserved characters out of the slug before persisting it — `BaseDashboardSchema.post_load` in `superset/dashboards/schemas.py` runs `re.sub(r"[^\w\-]+", "", ...)` — so the persisted slug returned in the `PUT /api/v1/dashboard/{id}` response can differ from what was submitted. Building the redirect from the raw value produces e.g. `/dashboard/?test/`, which the router resolves to a slug-less `/dashboard/` and renders blank on first paint.
**Fix.** Build the redirect from the slug in the update response (`updatedDashboard.slug`), falling back to `id` when the response carries no slug:
```ts
const updatedSlug = updatedDashboard.slug as string | null | undefined;
navigateWithState(`/dashboard/${updatedSlug || id}/`, { event: 'dashboard_properties_changed' });
```
The Copy / *Save as* path (`onCopySuccess`) already redirects on the response `id` only and is unaffected. The change is one decision point plus regression tests.
### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Captured in a real dev environment at a fixed 1280×800 viewport. Scenario (identical for both): log in → open the *USA Births Names* dashboard → **Edit dashboard** → **⋯ → Edit properties** → set **URL Slug** to `?test` → **Apply** → **Save** → observe the address bar on first render (no manual reload). A `location.href` banner is injected into each still because Playwright screenshots don't include browser chrome.
**Before (master)** — post-save URL is `/dashboard/` with the slug lost; the dashboard renders **blank**:


**After (this PR)** — post-save URL is the sanitized `/dashboard/test/`; the dashboard **renders correctly**:


Full screen recordings (VP8 WebM): [before-master.webm](https://raw.githubusercontent.com/sadpandajoe/superset/pr-assets-sc107323/pr-assets/sc107323/before-master.webm) · [after-fix.webm](https://raw.githubusercontent.com/sadpandajoe/superset/pr-assets-sc107323/pr-assets/sc107323/after-fix.webm). Capture script: [capture.mjs](https://raw.githubusercontent.com/sadpandajoe/superset/pr-assets-sc107323/pr-assets/sc107323/capture.mjs).
### TESTING INSTRUCTIONS
Manual:
1. Open any dashboard, enter edit mode, open **⋯ → Edit properties**.
2. Set **URL Slug** to a value starting with a reserved character, e.g. `?test`, and **Save**.
3. On `master` the first render is blank (URL missing the dashboard); with this change the redirect goes to `/dashboard/test/` (the sanitized slug) and the dashboard renders. A slug of only reserved characters (e.g. `?`) sanitizes to empty and correctly falls back to `/dashboard/<id>/`.
Automated (`superset-frontend`):
```
npm run test -- src/dashboard/actions/dashboardState.test.ts
```
Two regression tests were added: (a) submitted slug `?test` + PUT-response slug `test` ⇒ redirect `/dashboard/test/`; (b) PUT-response slug empty/null ⇒ redirect falls back to `/dashboard/<id>/`. Both fail on `master` and pass with this change.
### ADDITIONAL INFORMATION
<!--- Check any relevant boxes with "x" -->
- [ ] Has associated issue:
- [ ] Required feature flags:
- [x] Changes UI
- [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351))
- [ ] Introduces new feature or API
- [ ] Removes existing feature or API
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "sadpandajoe (via GitHub)" <gi...@apache.org>.
sadpandajoe merged PR #42853:
URL: https://github.com/apache/superset/pull/42853
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #42853:
URL: https://github.com/apache/superset/pull/42853#issuecomment-5208044075
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "netlify[bot] (via GitHub)" <gi...@apache.org>.
netlify[bot] commented on PR #42853:
URL: https://github.com/apache/superset/pull/42853#issuecomment-5208029649
### <span aria-hidden="true">✅</span> Deploy Preview for *superset-docs-preview* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d0cf5df302d5953a6e9a9020046f22addb12e453 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/projects/superset-docs-preview/deploys/6a74cb06540d24000834a269 |
|<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-42853--superset-docs-preview.netlify.app](https://deploy-preview-42853--superset-docs-preview.netlify.app) |
|<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br /><br /><br />_Use your smartphone camera to open QR code link._</details> |
|<span aria-hidden="true">🤖</span> Make changes | [Run an agent on this branch](https://app.netlify.com/projects/superset-docs-preview/agent-runs#FctRCoQgEIDhu8xzwtCa1d6gY4yOW0KljAbVsndfe_v54ftCkrilAm-ABqzQ7pban3AqprzYSMIqr8esxHMQ74rKtIcSbs_PilWxT2u8Jq7OUK-dRdNp5FYj4vDS1JoRfn8) |
---
<!-- [superset-docs-preview Preview](https://deploy-preview-42853--superset-docs-preview.netlify.app) -->
_To edit notification comments on pull requests, go to your [Netlify project configuration](https://app.netlify.com/projects/superset-docs-preview/configuration/notifications#deploy-notifications)._
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "Copilot (via GitHub)" <gi...@apache.org>.
Copilot commented on code in PR #42853:
URL: https://github.com/apache/superset/pull/42853#discussion_r3732490584
##########
superset-frontend/src/dashboard/actions/dashboardState.test.ts:
##########
@@ -298,6 +298,80 @@ describe('dashboardState actions', () => {
{ event: 'dashboard_properties_changed' },
);
});
+
+ // Regression for the reserved-URL-character slug redirect. When the
+ // submitted slug starts with a reserved character (e.g. `?` or `/`), the
+ // backend sanitizes it out of the persisted slug
+ // (BaseDashboardSchema.post_load strips `[^\w\-]`). The post-save redirect
+ // must therefore be built from the sanitized slug returned in the PUT
+ // response, not the raw slug the user submitted, or the first render lands
+ // on a malformed/blank URL (a later reload works because it reads the
+ // stored, sanitized slug).
+ test('redirects using the sanitized slug from the PUT response, not the raw submitted slug', async () => {
+ const updatedId = 778;
+ const { getState, dispatch } = setup({
+ dashboardState: { hasUnsavedChanges: true },
+ });
+
+ mockNavigateWithState.mockClear();
+ putStub.mockRestore();
+ putStub = jest.spyOn(SupersetClient, 'put').mockResolvedValue({
+ json: {
+ result: { ...mockDashboardData, id: updatedId, slug: 'test' },
+ last_modified_time: 0,
+ },
+ } as any);
+
+ const thunk = saveDashboardRequest(
+ { ...newDashboardData, slug: '?test' },
+ updatedId,
+ SAVE_TYPE_OVERWRITE,
+ );
+ await thunk(dispatch, getState);
+
+ await waitFor(() => expect(putStub.mock.calls.length).toBe(1));
+ await waitFor(() => expect(mockNavigateWithState).toHaveBeenCalled());
+
+ expect(mockNavigateWithState).toHaveBeenCalledWith('/dashboard/test/', {
+ event: 'dashboard_properties_changed',
+ });
+ });
+
+ // Regression companion: when the PUT response carries no usable slug (null
+ // or empty after sanitization — e.g. a slug composed solely of reserved
+ // characters sanitizes down to an empty string), the redirect must fall
+ // back to the dashboard id rather than emitting `/dashboard//` or echoing
+ // the raw submitted slug.
+ test('redirects using the id when the PUT response slug is empty', async () => {
+ const updatedId = 779;
+ const { getState, dispatch } = setup({
+ dashboardState: { hasUnsavedChanges: true },
+ });
+
+ mockNavigateWithState.mockClear();
+ putStub.mockRestore();
+ putStub = jest.spyOn(SupersetClient, 'put').mockResolvedValue({
+ json: {
+ result: { ...mockDashboardData, id: updatedId, slug: null },
+ last_modified_time: 0,
+ },
Review Comment:
The backend slug sanitization (BaseDashboardSchema.post_load) can turn a submitted slug like "?" into an empty string (""), not `null`. This test currently stubs the PUT response with `slug: null`, so it doesn't exercise the real "sanitized to empty string" redirect case that the production bug describes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #42853:
URL: https://github.com/apache/superset/pull/42853#issuecomment-5210084404
<!-- Bito Reply -->
The test case `redirects using the id when the PUT response slug is empty` in `superset-frontend/src/dashboard/actions/dashboardState.test.ts` currently mocks the PUT response with `slug: null`. To accurately test the production bug where the backend sanitizes a submitted slug like `?` into an empty string (`""`), the mock should be updated to return `slug: ""` instead of `slug: null`.
This change will ensure the test exercises the logic where `updatedSlug` becomes an empty string, verifying that the code correctly falls back to the dashboard `id` for the redirect URL.
**superset-frontend/src/dashboard/actions/dashboardState.test.ts**
```
putStub = jest.spyOn(SupersetClient, 'put').mockResolvedValue({
json: {
result: { ...mockDashboardData, id: updatedId, slug: '' },
last_modified_time: 0,
},
} as any);
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on code in PR #42853:
URL: https://github.com/apache/superset/pull/42853#discussion_r3752571220
##########
superset-frontend/src/dashboard/actions/dashboardState.test.ts:
##########
@@ -298,6 +298,80 @@ describe('dashboardState actions', () => {
{ event: 'dashboard_properties_changed' },
);
});
+
+ // Regression for the reserved-URL-character slug redirect. When the
+ // submitted slug starts with a reserved character (e.g. `?` or `/`), the
+ // backend sanitizes it out of the persisted slug
+ // (BaseDashboardSchema.post_load strips `[^\w\-]`). The post-save redirect
+ // must therefore be built from the sanitized slug returned in the PUT
+ // response, not the raw slug the user submitted, or the first render lands
+ // on a malformed/blank URL (a later reload works because it reads the
+ // stored, sanitized slug).
+ test('redirects using the sanitized slug from the PUT response, not the raw submitted slug', async () => {
+ const updatedId = 778;
+ const { getState, dispatch } = setup({
+ dashboardState: { hasUnsavedChanges: true },
+ });
+
+ mockNavigateWithState.mockClear();
+ putStub.mockRestore();
+ putStub = jest.spyOn(SupersetClient, 'put').mockResolvedValue({
+ json: {
+ result: { ...mockDashboardData, id: updatedId, slug: 'test' },
+ last_modified_time: 0,
+ },
+ } as any);
+
+ const thunk = saveDashboardRequest(
+ { ...newDashboardData, slug: '?test' },
+ updatedId,
+ SAVE_TYPE_OVERWRITE,
+ );
+ await thunk(dispatch, getState);
+
+ await waitFor(() => expect(putStub.mock.calls.length).toBe(1));
+ await waitFor(() => expect(mockNavigateWithState).toHaveBeenCalled());
+
+ expect(mockNavigateWithState).toHaveBeenCalledWith('/dashboard/test/', {
+ event: 'dashboard_properties_changed',
+ });
+ });
+
+ // Regression companion: when the PUT response carries no usable slug (null
+ // or empty after sanitization — e.g. a slug composed solely of reserved
+ // characters sanitizes down to an empty string), the redirect must fall
+ // back to the dashboard id rather than emitting `/dashboard//` or echoing
+ // the raw submitted slug.
+ test('redirects using the id when the PUT response slug is empty', async () => {
+ const updatedId = 779;
+ const { getState, dispatch } = setup({
+ dashboardState: { hasUnsavedChanges: true },
+ });
+
+ mockNavigateWithState.mockClear();
+ putStub.mockRestore();
+ putStub = jest.spyOn(SupersetClient, 'put').mockResolvedValue({
+ json: {
+ result: { ...mockDashboardData, id: updatedId, slug: null },
+ last_modified_time: 0,
+ },
Review Comment:
Good catch, `post_load` sanitizes reserved characters down to an empty string, not null. Updated the mock to `slug: ''` so the test actually exercises that path.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #42853:
URL: https://github.com/apache/superset/pull/42853#issuecomment-5246652967
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
<details>
<summary>
Bito Usage Guide
</summary>
**Commands**
Type the following command in the pull request comment and save the comment.
- `/review` - Manually triggers a full AI review.
- `/pause` - Pauses automatic reviews on this pull request.
- `/resume` - Resumes automatic reviews.
- `/resolve` - Marks all Bito-posted review comments as resolved.
- `/abort` - Cancels all in-progress reviews.
Refer to the <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/available-commands" target="_blank" rel="noopener noreferrer">documentation</a> for additional commands.
**Configuration**
This repository uses `Superset` You can customize the agent settings <a href="https://alpha.bito.ai/home/ai-agents/code-review-agent" target="_blank" rel="noopener noreferrer">here</a> or contact your Bito workspace admin at evan@preset.io.
**Documentation & Help**
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/getting-started/install-run-using-bito-cloud/create-or-customize-an-agent-instance" target="_blank" rel="noopener noreferrer">Customize agent settings</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/implementing-custom-code-review-rules" target="_blank" rel="noopener noreferrer">Review rules</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent" target="_blank" rel="noopener noreferrer">General documentation</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/faqs" target="_blank" rel="noopener noreferrer">FAQ</a>
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "codecov[bot] (via GitHub)" <gi...@apache.org>.
codecov[bot] commented on PR #42853:
URL: https://github.com/apache/superset/pull/42853#issuecomment-5210194512
## [Codecov](https://app.codecov.io/gh/apache/superset/pull/42853?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 65.73%. Comparing base ([`de93a19`](https://app.codecov.io/gh/apache/superset/commit/de93a19b3c78495df5c33f621ed2f1029bdf877a?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)) to head ([`d0cf5df`](https://app.codecov.io/gh/apache/superset/commit/d0cf5df302d5953a6e9a9020046f22addb12e453?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
:warning: Report is 10 commits behind head on master.
<details><summary>Additional details and impacted files</summary>
```diff
@@ Coverage Diff @@
## master #42853 +/- ##
==========================================
- Coverage 65.73% 65.73% -0.01%
==========================================
Files 2843 2843
Lines 162659 162660 +1
Branches 37239 37239
==========================================
Hits 106921 106921
- Misses 53645 53646 +1
Partials 2093 2093
```
| [Flag](https://app.codecov.io/gh/apache/superset/pull/42853/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | |
|---|---|---|
| [javascript](https://app.codecov.io/gh/apache/superset/pull/42853/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `72.09% <100.00%> (-0.01%)` | :arrow_down: |
Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#carryforward-flags-in-the-pull-request-comment) to find out more.
</details>
[:umbrella: View full report in Codecov by Harness](https://app.codecov.io/gh/apache/superset/pull/42853?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
:loudspeaker: Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
<details><summary> :rocket: New features to boost your workflow: </summary>
- :snowflake: [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
- :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(dashboard): redirect using sanitized slug from save response [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #42853:
URL: https://github.com/apache/superset/pull/42853#issuecomment-5211087200
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
<details>
<summary>
Bito Usage Guide
</summary>
**Commands**
Type the following command in the pull request comment and save the comment.
- `/review` - Manually triggers a full AI review.
- `/pause` - Pauses automatic reviews on this pull request.
- `/resume` - Resumes automatic reviews.
- `/resolve` - Marks all Bito-posted review comments as resolved.
- `/abort` - Cancels all in-progress reviews.
Refer to the <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/available-commands" target="_blank" rel="noopener noreferrer">documentation</a> for additional commands.
**Configuration**
This repository uses `Superset` You can customize the agent settings <a href="https://alpha.bito.ai/home/ai-agents/code-review-agent" target="_blank" rel="noopener noreferrer">here</a> or contact your Bito workspace admin at evan@preset.io.
**Documentation & Help**
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/getting-started/install-run-using-bito-cloud/create-or-customize-an-agent-instance" target="_blank" rel="noopener noreferrer">Customize agent settings</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/implementing-custom-code-review-rules" target="_blank" rel="noopener noreferrer">Review rules</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent" target="_blank" rel="noopener noreferrer">General documentation</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/faqs" target="_blank" rel="noopener noreferrer">FAQ</a>
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org