Skip to content

Conversation

@averikitsch
Copy link
Collaborator

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

@averikitsch averikitsch requested a review from a team as a code owner February 22, 2024 23:30
@conventional-commit-lint-gcf
Copy link

conventional-commit-lint-gcf bot commented Feb 22, 2024

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/langchain-google-spanner-python API. label Feb 22, 2024
@averikitsch averikitsch requested a review from kurtisvg February 22, 2024 23:58
@averikitsch averikitsch merged commit e9eb86b into main Feb 23, 2024
@averikitsch averikitsch deleted the averikitsch-patch-1 branch February 23, 2024 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the googleapis/langchain-google-spanner-python API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants