Skip to content

[GSK-3568] Remove legacy hub mentions from docs #1942

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
Merged
henchaves merged 26 commits into from
May 30, 2024
Merged

[GSK-3568] Remove legacy hub mentions from docs #1942

henchaves merged 26 commits into from
May 30, 2024

Conversation

@henchaves
Copy link
Member

@henchaves henchaves commented May 28, 2024 •
edited
Loading

Description

Related Issue

Type of Change

  • 📚 Examples / docs / tutorials / dependencies update
  • 🔧 Bug fix (non-breaking change which fixes an issue)
  • 🥂 Improvement (non-breaking change which improves an existing feature)
  • 🚀 New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 🔐 Security fix

Checklist

  • I've read the CODE_OF_CONDUCT.md document.
  • I've read the CONTRIBUTING.md guide.
  • I've written tests for all new methods and classes that I created.
  • I've written the docstring in Google format for all the methods and classes that I used.
  • I've updated the pdm.lock running pdm update-lock (only applicable when pyproject.toml has been
    modified)

@linear
Copy link

linear bot commented May 28, 2024

GSK-3568 Remove all mentions to Legacy Hub on `giskard` docs/API

@henchaves henchaves changed the title Feature/gsk 3568 remove all mentions to legacy hub on giskard docsapi [WIP] [GSK-3568] Remove legacy hub mentions from docs May 29, 2024
@sonarqubecloud
Copy link

sonarqubecloud bot commented May 29, 2024

Please retry analysis of this Pull-Request directly on SonarCloud

@sonarqubecloud
Copy link

sonarqubecloud bot commented May 29, 2024

Please retry analysis of this Pull-Request directly on SonarCloud

@sonarqubecloud
Copy link

sonarqubecloud bot commented May 29, 2024

Please retry analysis of this Pull-Request directly on SonarCloud

@sonarqubecloud
Copy link

sonarqubecloud bot commented May 29, 2024

Please retry analysis of this Pull-Request directly on SonarCloud

@kevinmessiaen
Ran LLM QA Documentation
fdbb7c7
@kevinmessiaen
Merge remote-tracking branch 'origin/feature/gsk-3568-remove-all-ment…
db7b50f 
…ions-to-legacy-hub-on-giskard-docsapi' into feature/gsk-3568-remove-all-mentions-to-legacy-hub-on-giskard-docsapi
@sonarqubecloud
Copy link

sonarqubecloud bot commented May 30, 2024

Please retry analysis of this Pull-Request directly on SonarCloud

@henchaves henchaves marked this pull request as ready for review May 30, 2024 08:08
@henchaves henchaves changed the title [WIP] [GSK-3568] Remove legacy hub mentions from docs [GSK-3568] Remove legacy hub mentions from docs May 30, 2024
@henchaves henchaves requested a review from kevinmessiaen May 30, 2024 08:13
kevinmessiaen
kevinmessiaen reviewed May 30, 2024
View reviewed changes
kevinmessiaen
kevinmessiaen reviewed May 30, 2024
View reviewed changes
@sonarqubecloud
Copy link

sonarqubecloud bot commented May 30, 2024

Please retry analysis of this Pull-Request directly on SonarCloud

@henchaves henchaves added the documentation Improvements or additions to documentation label May 30, 2024
@sonarqubecloud
Copy link

sonarqubecloud bot commented May 30, 2024

Please retry analysis of this Pull-Request directly on SonarCloud

@henchaves henchaves merged commit 6135e13 into main May 30, 2024
@henchaves henchaves deleted the feature/gsk-3568-remove-all-mentions-to-legacy-hub-on-giskard-docsapi branch May 30, 2024 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kevinmessiaen kevinmessiaen kevinmessiaen approved these changes

Assignees

No one assigned

Labels

documentation Improvements or additions to documentation

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@henchaves @kevinmessiaen