Repository navigation
ci: add centralized docs drift check - #3200
Open
joe-clickhouse wants to merge 1 commit into
Open
joe-clickhouse wants to merge 1 commit into
joe-clickhouse wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds the shared docs-drift check already used by clickhouse-connect, dbt-clickhouse, and clickhouse-go. It reviews PR changes against this repo's docs and maintains an advisory
needs-docslabel and one sticky comment. A later docs fix clears the label and marks the comment resolved.The custom agent definition is a solid first attempt based on the repo's current docs and public APIs. It covers current and legacy clients, JDBC, R2DBC, shared types, packaging, examples, and
docs/features.md, with particular attention to formats, resource lifetimes, conversions, and optional dependencies. We can update or change it at any time, before or after this PR merges.Automatic checks skip fork and Dependabot PRs. Maintainers can check reviewed PRs manually. The worker reads the agent definition from the trusted PR base, so this will start taking effect after merge.
This changes CI only. Java APIs and runtime behavior stay unchanged.
Checklist