-
Notifications
You must be signed in to change notification settings - Fork 473
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
API reference documentation #782
Conversation
I would appreciate if we setup the CI such that it doesn't require a branch from the same repo, and having the initial PR from a separate repo would make sure the CI runs fine. If we expect this to be something that multiple people work one, we could have a branch in the repo for it, and have PRs to that branch instead of |
Regarding the CI: yes, that is the goal, but it is not ready right now and needs iteration, which I hope to do right here. Regarding the second point, I'm not sure I understand; that is absolutely the goal as well. I am creating an initial commit on a feature branch, which takes care of most of the work. As you can see, it is not yet ready as the CI did not run, a very important step in order to collaborate on this specific branch. We can then work on that branch through PRs as you mention, once I set this branch as ready for contributions. How would you have managed this differently? |
Fair enough. I though you meant for people to directly push to this branch. I'm happy if people push to this branch through PRs from their forks. I would create a branch with no changes, and then create a PR from my fork to that branch with the initial changes you're proposing here. But that's a minor difference. I'm happy with what you propose :) |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. |
We should be good to go to work on this feature branch now. As mentioned by the bot above, the development can be seen directly on the following URL: https://moon-ci-docs.huggingface.co/docs/huggingface_hub/pr_782/en/index From what I've seen, here are the remaining steps: The following high-level objectives need to be handled
The following methods have not yet been checked for their documentation:
|
Not sure if I understand. So you mean we can now send PRs to this branch? |
Yes, that's what I mean! |
Opened a first PR here which takes care of all the remaining methods mentioned above: #799 |
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.
Same with long lines and hyperlink issues here.
* Finalize docstrings * Endpoint helpers * Run on doc-frontend target * It was just another GitHub Actions issue * Address review comments Co-authored-by: Adrin Jalali <adrin.jalali@gmail.com> * Address review comments * Add deprecation warnings * Precise deprecation warnings Co-authored-by: Adrin Jalali <adrin.jalali@gmail.com>
PR was merged, but GitHub Actions didn't launch the workflow (it seems to be down) to update the documentation yet, please be aware of it when reviewing if checking the documentation. Since the delete documentation didn't launch either, the documentation of this PR with the commit above can be seen here |
@stevhliu, @osanseviero, could you take a look at this PR? Would love to hear your feedback about the content. This will likely be put at https://huggingface.co/docs/python-wrapper |
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.
Very nice, thank you for this PR! I did a pass through most files (missing repository
and endpoint_helpers
to make sure they are consistent.
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.
This is great, I learned a lot from reading this! 🎉
What do you think about adding a brief code example for each function like you already have for the DatasetFilter
section? This could help cover functions/methods we don't explicitly cover in the tutorials/guides (maybe because they aren't commonly used but they're still useful).
It'd be quite a bit to add though so we can always tackle it in a later PR. ❤️
Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com> Co-authored-by: Omar Sanseviero <osanseviero@gmail.com>
For consistency I would rather serve the doc at |
This PR should be ready to be merged. When merged, I would like to open issues for the following:
If this looks good to you, @osanseviero @stevhliu, I'll merge this PR. |
@@ -0,0 +1,24 @@ | |||
- sections: |
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 think a title
should also be added here (like below with title: "Reference"
).
https://moon-ci-docs.huggingface.co/docs/huggingface_hub/pr_782/en/index
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.
Indeed, good catch! Will add this.
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.
Happy to merge and improve on smaller PRs. This is already too large.
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.
This is great, thanks!
Thanks all for the reviews, all green, merging this PR! Will open a few relevant issues as discussed above. |
Work in progress aiming to supply an API reference for the huggingface_hub python library.
Done from a feature branch as many may collaborate on the branch and it will be easier to setup the GitHub Actions CI in a first step.