-
Notifications
You must be signed in to change notification settings - Fork 126
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
CI: sync API docs with readme.com #266
Conversation
f4276e9
to
00cee9a
Compare
aa15438
to
2d1b7c1
Compare
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.
LGTM! The suggestion's optional. Feel free to merge (or not).
If we merge this workflow, it would fail for integration that don't support hatch run docs yet. Not sure if we should wait, let it fail, or add safeguards to skip the job when hatch run docs is not available
Just a thought: A probable outcome of skipping the job will be our procrastinating adding support for hatch in those integrations 😄 If it's not a lot of work, we might want to prioritize it.
Do not merge until #274 is complete |
test commit, to be reverted Revert "test commit, to be reverted" This reverts commit b9997f7.
fine tune action settings try try try try
Co-authored-by: Madeesh Kannan <[email protected]>
This reverts commit 3538b01.
74eed06
to
a8d8964
Compare
When changes to
integrations/*
are merged onmain
:Note for the reviewer:
hatch run docs
yet. Not sure if we should wait, let it fail, or add safeguards to skip the job whenhatch run docs
is not available