Skip to content

Conversation

@vietluong2110
Copy link

Before submitting a pull request (PR), please read the contributing guide.

Please fill out as much of this template as you can, but if you have any problems or questions, just leave a comment and we will help out :)

Description

What is this PR

  • [] Bug fix
  • Addition of a new feature
  • Other

Why is this PR needed?

What does this PR do?

References

Please reference any existing issues/PRs that relate to this PR.
#67

How has this PR been tested?

Please explain how any new code has been tested, and how you have ensured that no existing functionality has changed.

Is this a breaking change?

If this PR breaks any existing functionality, please explain how and why.

Does this PR require an update to the documentation?

If any features have changed, or have been added. Please explain how the
documentation has been updated.

Checklist:

  • The code has been tested locally
  • Tests have been added to cover all new functionality
  • The documentation has been updated to reflect any changes
  • The code has been formatted with pre-commit

@sfmig
Copy link
Member

sfmig commented Mar 28, 2025

Hi @vietluong2110 thanks for having a go!

Would you mind reviewing the CI checks failures? There seem to be issues with linting and pre-commit formatting. Do have a read on the contributing guidelines if you haven't already, it clarifies a bit what these checks do.

@vietluong2110
Copy link
Author

@sfmig yes, I'll take a look at the CI checks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants