Skip to content

Conversation

@SaboniAmine
Copy link
Member

Description

Please explain the changes you made here.

Related Issue

Please link to the issue this PR resolves: [issue #]

Motivation and Context

Why is this change required? What problem does it solve?

How Has This Been Tested?

Please describe in detail how you tested your changes.

Screenshots (if appropriate):

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING.md document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@SaboniAmine SaboniAmine requested a review from inimaz July 1, 2025 06:54
Copy link
Collaborator

@inimaz inimaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks!

@SaboniAmine SaboniAmine force-pushed the fix/fix_clever_deployment branch from 52a74b2 to 4c40e52 Compare July 1, 2025 08:02
@inimaz inimaz merged commit 9722956 into master Jul 1, 2025
5 checks passed
@inimaz inimaz deleted the fix/fix_clever_deployment branch July 1, 2025 08:52
@benoit-cty benoit-cty mentioned this pull request Jul 11, 2025
6 tasks
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.

3 participants