What log retention and alerting gaps exist in cPanel Git deployment logging for production diagnostics?
Context cPanel v100+ stores Git deployment logs in each repository's .cpanel/logs/deploy.log and surfaces the last 100 lines in the "Deployment Logs" UI. The interface marks failed runs with a red status but does not rotate logs, enforce quotas, or emit failure notifications by default. Problem Without built-in log rotation, the log file grows indefinitely a
cpanel