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

Update README.md #1532

Merged
merged 1 commit into from
May 29, 2023
Merged

Update README.md #1532

merged 1 commit into from
May 29, 2023

Conversation

ricklamers
Copy link
Member

Description

Description (including a screenshot/video if applicable) of what your PR solves or adds.

Fixes: #issue

Checklist

  • I have manually tested my changes and I am happy with the result.
  • The documentation reflects the changes.
  • The PR branch is set up to merge into dev instead of master.
  • I haven't introduced breaking changes that would disrupt existing jobs, i.e. backwards compatibility is maintained.
  • In case I changed the dependencies in any requirements.in I have run pip-compile to update the corresponding requirements.txt.
  • In case I changed one of the services' models.py I have performed the appropriate database migrations (refer to the DB migration docs).
  • In case I changed code in the orchest-sdk I followed its release checklist.
  • In case I changed code in the orchest-cli I followed its release checklist.

@ricklamers ricklamers merged commit e7d284a into master May 29, 2023
1 of 3 checks passed
@ricklamers ricklamers deleted the ricklamers-patch-1 branch May 29, 2023 04:18
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.

None yet

1 participant