-
Notifications
You must be signed in to change notification settings - Fork 180
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
Run regenerate_docs.sh #297
Conversation
Looks like the problem was reported last time someone touched the docs, but then not followed up? |
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.
Thank you for catching this! Agree with the PR, but I would like to limit it just to regenerating the docs and removing the obsolete --experimental_remap_main_repo flag.
|
||
for filename in bazel-bin/docs/*_gen.md; do |
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 would prefer to avoid changing the rename logic here (and thus avoid changing all the out
s in docs/BUILD) without a specific reason. The existing logic works, and "_gen" suffix in a generated doc file is a good signal.
docs/BUILD
Outdated
@@ -6,132 +6,132 @@ licenses(["notice"]) | |||
# the --incompatible_remap_main_repo flag. | |||
stardoc( | |||
name = "build_test_docs", | |||
out = "build_test_doc_gen.md", |
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 don't see a good reason for the out
renames here and below in docs/BUILD. "_gen" means a generated, not hand-written md doc.
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.
sure, I'll open a separate PR for that change and discuss my reasoning.
Seems that recent edits were done by hand? Is the generator script still functioning? - remove flag that no longer exists in recent bazel releases from regenerate_docs script - now uses markdown tables since that's what the pinned version of stardoc does
@tetromino is the intent for the docs to always be up-to-date? If so, the root cause here was a missing |
ping @tetromino would you like tests added here that assert the docs are always up-to-date? |
@alexeagle - yes, a test to check docs are up to date would be greatly appreciated (as a follow-up PR). |
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.
Thanks, looks good!
There are some conflicts reported - let me see if they can be fixed trivially...
it prints a convenient 'bazel run' command to update them, replacing the shell script Follow-up to bazelbuild#297 (comment)
it prints a convenient 'bazel run' command to update them, replacing the shell script Follow-up to bazelbuild#297 (comment)
it prints a convenient 'bazel run' command to update them, replacing the shell script Follow-up to bazelbuild#297 (comment)
it prints a convenient 'bazel run' command to update them, replacing the shell script Follow-up to bazelbuild#297 (comment)
Seems that recent edits were done by hand? Is the generator script still functioning?