-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Add plugin list to docs that is generated from the repo #71731
Add plugin list to docs that is generated from the repo #71731
Conversation
This is awesome, thanks!! The only thing I want to play around with is if we change our README.mds to README.asciidocs. After some exploration is looks like asciidoc is not rendered that great inside github itself (no support for But I think it would be better if the plugin link was part of the asciidoc book and not a direct link to github. Going to see if I can get something decent working, if not, we can check it in with just markdown support for now. |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Co-authored-by: Stacey Gammon <gammon@elastic.co>
…erated-plugin-list-in-docs
So cool!! |
@stacey-gammon the note at the top, and especially the bash blurb, were a little gross looking for my taste. Since we are validating this in CI anyway I moved them to a comment and updated the check which makes CI optional to require CI when changes to this file are detected. (though github is struggling right now so those changes aren't showing up in the PR quite yet) |
@elasticmachine merge upstream |
Looks good! Yes, much nicer to hide the "don't edit this" so it's not rendererd. cc @KOTungseth or @lcawl - just want to pull your attention to this new file. There is a note at the top of the Is that sufficient to warn the docs team not to use the "edit" links to edit directly? It would break the ci. Actually @spalger - would the ci check run if I only made a direct edit to the |
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.
So excited!! 🎉 🎉 .
Yeah, I've extended the logic we use to determine if CI needs to run to make sure that CI runs all tasks if the |
@elasticmachine merge upstream |
Pinging @elastic/kibana-operations (Team:Operations) |
…erated-plugin-list-in-docs
…erated-plugin-list-in-docs
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
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.
That LGTM
Co-authored-by: Stacey Gammon <gammon@elastic.co> Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> # Conflicts: # src/dev/ci_setup/setup.sh
Co-authored-by: Stacey Gammon <gammon@elastic.co> Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> # Conflicts: # docs/developer/architecture/index.asciidoc # src/dev/ci_setup/setup.sh
#72138) Co-authored-by: Stacey Gammon <gammon@elastic.co> Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> # Conflicts: # src/dev/ci_setup/setup.sh
#72139) Co-authored-by: Stacey Gammon <gammon@elastic.co> Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Closes #71663
Generates a list of all plugins with links to their readmes and the first paragraph from the same file. When a readme doesn't exist for a plugin we instead link to the plugin directory and write a warning that the readme does not exist.
This docs file is generated by running
node scripts/build_plugin_list_docs
(please help me with this name) and is verified to be up-to-date by CI.