CLI-447 Use the declarative framework for migrations#319
CLI-447 Use the declarative framework for migrations#319damien-urruty-sonarsource wants to merge 1 commit into
Conversation
Agentic Analysis: Early ResultsAgentic Analysis and Context Augmentation are available on your project. Here are some issues that could have been prevented. Follow the links to learn how to put them into action. 1 issue(s) found across 1 file(s):
Analyzed by SonarQube Agentic Analysis in 4.9 s |
29b0ae0 to
8acb20b
Compare
8acb20b to
f97b118
Compare
Code Review ✅ ApprovedRefactors CLI migrations to utilize the declarative framework, ensuring robust integration registration and cleaner lifecycle management for feature updates. No issues found. OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change:
Was this helpful? React with 👍 / 👎 | Gitar |
f97b118 to
ef21db0
Compare
|

Summary by Gitar
migrateDeclarativeIntegrationstorunPostUpdateActionsto manage feature lifecycle and apply updates.hasInstalledDeclarativeIntegrationto prevent legacy hook migration when declarative integration is active.claudeIntegrationto use the declarative framework forsonar-secretshooks.createRemoveObsoleteA3sArtifactsOperationto cleanup legacy SQAA artifacts during migration.ensureBuiltInIntegrationsRegisteredtopost-update.tsto ensure all integrations are registered before migration.registerGitIntegrationsto prevent duplicate registration in the integration registry.git-tools.test.tsto verifyregisterGitIntegrationsis idempotent rather than throwing on duplicate registration.This will update automatically on new commits.