-
Notifications
You must be signed in to change notification settings - Fork 573
Add repositories: key Qwen, Meta-Llama, and OSS GPT repositories #4811
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4811 +/- ##
==========================================
+ Coverage 66.80% 67.89% +1.09%
==========================================
Files 230 249 +19
Lines 16602 19124 +2522
==========================================
+ Hits 11091 12985 +1894
- Misses 4808 5277 +469
- Partials 703 862 +159 🚀 New features to boost your workflow:
|
Hi Mike, we require DCO on all commits. Please see this link for how to fix this |
Signed-off-by: Mike Dolan <mikedolan@gmail.com>
That's odd because in the commit itself on GitHub, it shows I have a signed-off-by statement. I have VS Code set up to -s sign all my commits. ![]() |
Looks good now thanks, but your original commit didn't have it: a1a1f67 I want to do a quick check on these repos to make sure none of them actually have the multi-gig models in them. |
Not sure what I did wrong on the first pass - thanks for checking it and sorry for any confusion.
I believe all the larger weights and parameters files for these models are all stored on HuggingFace, not the GitHub repo. This should mostly be inference code, APIs, examples, etc. If I got any of that wrong and there is a large model file, I'd certainly understand the rationale to exclude the repo. |
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
What is the current behavior?
What is the new behavior (if this is a feature change)?**
Which issue(s) this PR fixes
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)