-
Notifications
You must be signed in to change notification settings - Fork 41
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
General housekeeping #54
Conversation
4e78b44
to
315e8cd
Compare
315e8cd
to
560ce1f
Compare
@@ -1,4 +1,4 @@ | |||
name: Create and publish a Docker image | |||
name: Build and Push |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build and Push Container Image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine reverting, but the reason I made these changes: "Build and Push" as the title of the workflow and "container" as what is being built and pushed. I think it displays nicely on the output.
README.md
Outdated
@@ -1,36 +1,41 @@ | |||
# Lingo - K8s LLM Proxy + Scaler | |||
# Lingo - The lightweight model proxy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do think we should add K8s in the title so it's clear that this only works on K8s and is very focused towards K8s.
What about one of these options?
- The lightweight ML Model proxy and autoscaler for K8s
- Lightweight K8s ML Proxy and Autoscaler
- K8s ML Proxy and Autoscaler
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about leaving the title block just the name (# Lingo
) and keeping the description in the description section of the repo? I feel like these are too long for an H1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly some opinions around naming.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Names look good based on screenshot
NOTE: No actual changes to testing code were made. Changes to workflow files are mostly for readability of files and also of the checks as displayed on PRs.