Skip to content

chore: Move both kSuite modules into a common parent module #1731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 7, 2025
Merged

chore: Move both kSuite modules into a common parent module #1731

merged 1 commit into from
Aug 7, 2025

Conversation

KevinBoulongne
Copy link
Contributor

@KevinBoulongne KevinBoulongne requested a review from a team August 6, 2025 07:44
@github-actions github-actions bot added the dependent This MR depends on another PR label Aug 6, 2025
@github-actions github-actions bot removed the dependent This MR depends on another PR label Aug 7, 2025
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 7, 2025

This PR/issue depends on:

@sonarqubecloud SonarQubeCloud
Copy link

sonarqubecloud bot commented Aug 7, 2025

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@KevinBoulongne KevinBoulongne merged commit 23f3788 into main Aug 7, 2025
6 checks passed
@KevinBoulongne KevinBoulongne deleted the merge-ksuite-modules branch August 7, 2025 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tevincent tevincent tevincent approved these changes

Assignees

@KevinBoulongne KevinBoulongne

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@KevinBoulongne @tevincent