jprakash db/test gh

[jprakash-db]

• Updated some lines
• Setting up hatch

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[Copilot]

Pull request overview

Updates the project README with additional sections, including a note about setting up the Python connector.

Changes:

• Added a new “Testing new lines” section to the README.
• Added a “How to setup the Python Connector” section mentioning Hatch-based setup.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The new section title "Testing new lines" and the sentence below it read like placeholder text and don’t communicate actionable testing guidance. Consider removing this section or replacing it with actual test instructions (e.g., how to run the existing pytest suite).

[Copilot]

Header uses "setup" as a verb; standard usage is "set up" (two words) for the action. Please adjust the heading to "How to set up the Python Connector" for correctness and consistency.

Suggested change

	## How to setup the Python Connector
	## How to set up the Python Connector

[Copilot]

This line says the connector needs to be set up using Hatch, but the repository’s pyproject.toml is configured for Poetry (no Hatch configuration present). Either update the docs to reflect Poetry-based setup, or add the missing Hatch configuration/instructions if Hatch is intended going forward.

[Copilot]

Grammar/formatting: "needs to setup using hatch" should be "needs to be set up using Hatch" (and remove the double space).

Suggested change

	Python Connector needs to setup using hatch
	The Python connector needs to be set up using Hatch.