Return Non-Zero Exit Code On Failure

[lizard-boy]

🎟️ Tracking

📔 Objective

Return a non-zero exit code on failure so that github actions will mark a step that calls this project a failure if migrations could not be applied.

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

Greptile Summary

This pull request modifies the MsSqlMigratorUtility to return a non-zero exit code on failure, enabling GitHub Actions to detect migration failures accurately.

• Modified Execute method in /util/MsSqlMigratorUtility/Program.cs to return an integer (0 for success, 1 for failure)
• Ensures CI/CD pipelines can reflect the success or failure of database migration operations
• Improves error detection in automated workflows without changing core migration functionality

[greptile-apps]

LGTM

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}