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.

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

Refactoring api docs #169

Merged

Conversation

shreelakshmijoshi
Copy link
Collaborator

@shreelakshmijoshi shreelakshmijoshi commented Sep 4, 2024

  • Please refer to the code of conduct : link

  • Please check if the PR fulfills these requirements 📋

  • The commit message follows our guidelines : link
  • Docs have been added/updated (for bug fixes/features)
  • A new branch is created for the change(s) and the changes are not committed on the main or master branch
  • No credentials or secrets are committed
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, refactor, chore, test, config) 💁 📜
    refactor docs
    Removed CDPG logo from OpenAPI specs as it was not being rendered after deployment

  • Checklist for the current PR 📃

  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • New and existing unit tests pass locally with my changes

Removed CDPG logo from OpenAPI specs as it was not being rendered after deployment
Removed class TupleBuilder
Checking if the api docs link would change if the URL is recorrected using sed command
Trying to terminate the s command
@jenkins-datakaveri
Copy link

Build finished.

@shreelakshmijoshi shreelakshmijoshi merged commit 158b631 into datakaveri:main Sep 4, 2024
1 check passed
@jenkins-datakaveri
Copy link

Build finished.

3 similar comments
@jenkins-datakaveri
Copy link

Build finished.

@jenkins-datakaveri
Copy link

Build finished.

@jenkins-datakaveri
Copy link

Build finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants