Skip to content

Conversation

@dougthor42
Copy link
Collaborator

Part of #3082

First of probably 5 PRs.

  • Set up the Bazel config so that the rules_python root docs can reference and use the gazelle/docs directory.
  • Replace the original docs/gazelle.md with gazelle/docs/index.md
  • Migrate general info from gazelle/README.md to gazelle/docs/index.md
  • Mechanical updates:
    • Wrap at ~80 chars
    • Use MyST directives and roles.
  • Also a drive-by update to building and running docs without ibazel.

Part of bazel-contrib#3082

+ Set up the Bazel config so that the rules_python root docs can reference
  and use the gazelle/docs directory.
+ Replace the original docs/gazelle.md with gazelle/docs/index.md
+ Migrate general info from gazelle/README.md to gazelle/docs/index.md
+ Also a drive-by update to building and running docs _without_
  `ibazel`.
@dougthor42 dougthor42 marked this pull request as ready for review August 1, 2025 06:54
@dougthor42 dougthor42 added type: documentation gazelle Gazelle plugin related issues labels Aug 1, 2025
Copy link
Collaborator

@aignas aignas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, only nits, I'll approve and you can merge when you are done.

# Gazelle Plugin

[Gazelle][gazelle] is a build file generator for Bazel projects. It can
create new {code}`BUILD` or {code}`BUILD.bazel` files for a project that
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit:

Suggested change
create new {code}`BUILD` or {code}`BUILD.bazel` files for a project that
create new `BUILD` or `BUILD.bazel` files for a project that

I would expect this to be still markdown enough so that the above works.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done for all instances.

Are there any specific instances where {code} should be kept?

@dougthor42 dougthor42 added this pull request to the merge queue Aug 2, 2025
Merged via the queue into bazel-contrib:main with commit 39703fa Aug 2, 2025
3 checks passed
@dougthor42 dougthor42 deleted the u/dthor/gazelle-refactor-docs-pt1-core branch August 2, 2025 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gazelle Gazelle plugin related issues type: documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants