Conversation
There was a problem hiding this comment.
Pull request overview
Adds a Context7 configuration file to the repository and adjusts README badges to better reflect what’s highlighted at the top of the project page.
Changes:
- Add
context7.jsonwith project metadata and exclusion rules. - Remove Conformance + Codecov badges from the README header.
- Move the DeepWiki badge into the “Documentation” section.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| context7.json | Introduces Context7 configuration, including excluded folders/files. |
| README.md | Simplifies top-level badges and relocates DeepWiki badge to the docs section. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
| See the [samples overview](./samples/README.md) for a comparison table and detailed descriptions. | ||
|
|
||
| ## Documentation | ||
| [](https://deepwiki.com/modelcontextprotocol/kotlin-sdk) |
There was a problem hiding this comment.
it worths moving the documentation section after the TOC
There was a problem hiding this comment.
Perhaps, though I'm not sure
For now, since we only have generated dokka documentation, it may be too early to do that. Once we add proper full documentation, it would probably make sense to place it upper
| [](https://github.com/modelcontextprotocol/kotlin-sdk/actions/workflows/conformance.yml) | ||
| [](https://codecov.io/github/modelcontextprotocol/kotlin-sdk) |
There was a problem hiding this comment.
We should retain the badges. They are important operational indicators.
There was a problem hiding this comment.
important operational indicators
What is the practical value of these indicators?
- conformance test - when a baseline exists, this indicator does not always reflect the actual state of the project and can even be misleading in some cases. A badge for the main CI build is usually sufficient, adding badges for multiple CI workflows feels redundant
- codecov - coverage numbers without context provide limited value on their own. I doubt this is genuinely useful for users or contributors. Especially since each PR already includes a coverage report, which is usually sufficient
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context