Fix the script that generates TFJava doc #2332
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Hi, checking again if we can get some help, since updating the documentation on the website is pretty much the last thing remaining for us before publishing TF Java 1.0.0 cc\ @MarkDaoust |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, we (SIG-JVM) would like the TensorFlow Java API docs to be updated on the TensorFlow website.
We are sending you this script used to generated the Javadoc files, but unless the process has changed, the script should be retrieved from our own repo under that location. So one main reason to create this PR was also to find a way to reach out to you to share our intent (btw is there another communication channel that we can use other than GitHub PRs?). It is an update from the one @MarkDaoust originally contributed to our repo.
In addition, we have updated the install instructions that you can retrieve here.
We are happy to refactor this process as well, we are not sure anymore where that script should live.