Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
DOC: add API docs content guidelines to api docs instructions#30085
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
Remark: I would be hesitant to claim somebody knows "API" if they don't know "docstring". Either may be the case, but generally, I'd expect that most people wo can meaningfully update this know both. My primary reason for suggesting renaming is that API documentation is more general and we can put "inheritance diagrams" under that topic as well. |
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.
May self-merge after removing "new or edited"
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
@timhoffm you didn't approve so I can't merge 😭
Sorry for the mischaracterization, I was thinking more of how we were discussing orienting around purpose (why they need to know this tech) rather than the specific tech. |
1c84927
intomatplotlib:mainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
PR summary
PR checklist