Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: add a FAQ about asset recovery from UI #25482

Merged
merged 4 commits into from
Oct 3, 2023
Merged

docs: add a FAQ about asset recovery from UI #25482

merged 4 commits into from
Oct 3, 2023

Conversation

mdeshmu
Copy link
Contributor

@mdeshmu mdeshmu commented Oct 1, 2023 •
edited
Loading

SUMMARY

Address bugherd task 35

cc: @sfirke @rusackas

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@mdeshmu mdeshmu changed the title docs: add an FAQ about asset recovery from UI docs: add a FAQ about asset recovery from UI Oct 2, 2023
@mdeshmu
Copy link
Contributor Author

mdeshmu commented Oct 2, 2023

pre-commit failure is not related to this PR.

tests/unit_tests/db_engine_specs/test_clickhouse.py:66: error: Argument 1 to "NewConnectionError" has incompatible type "str"; expected "HTTPConnection" [arg-type]

@john-bodley john-bodley requested a review from sfirke October 2, 2023 16:56
@john-bodley
Copy link
Member

@mdeshmu would you mind providing links to the issues you mentioned to aid with context?

sfirke
sfirke approved these changes Oct 2, 2023
View reviewed changes
Copy link
Member

@sfirke sfirke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@sfirke
Copy link
Member

sfirke commented Oct 2, 2023

@john-bodley do you mean the referenced BugHerd issue? It's at https://www.bugherd.com/projects/334204/tasks/35, let me know if you'd like me to add you to the BugHerd tracker if you're not already on there.

@sfirke sfirke added the merge-if-green If approved and tests are green, please go ahead and merge it for me label Oct 2, 2023
@mdeshmu
Copy link
Contributor Author

mdeshmu commented Oct 3, 2023

This is ready to merge

@sfirke sfirke merged commit 789e6b7 into apache:master Oct 3, 2023
@sfirke
Copy link
Member

sfirke commented Oct 3, 2023

thanks for all the docs PRs @mdeshmu !

@mdeshmu mdeshmu deleted the bugherd-35 branch October 13, 2023 15:26
cccs-rc pushed a commit to CybercentreCanada/superset that referenced this pull request Mar 6, 2024
@mdeshmu @sfirke
docs: add a FAQ about asset recovery from UI (apache#25482)
b04a160 
Co-authored-by: Sam Firke <sfirke@users.noreply.github.com>
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 3.1.0 labels Mar 8, 2024
vinothkumar66 pushed a commit to vinothkumar66/superset that referenced this pull request Nov 11, 2024
@mdeshmu @sfirke
docs: add a FAQ about asset recovery from UI (apache#25482)
f4e3139 
Co-authored-by: Sam Firke <sfirke@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sfirke sfirke sfirke approved these changes

Assignees
No one assigned
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels merge-if-green If approved and tests are green, please go ahead and merge it for me size/XS 🚢 3.1.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@mdeshmu @john-bodley @sfirke @mistercrunch