Fix React DOM warnings and improve pre-push hook
Some checks failed
CI/CD Pipeline (Simple) / test-and-build (push) Has been cancelled
CI/CD Pipeline (Simple) / production (push) Has been cancelled

- Fix fill and priority boolean attributes in Hero component
- Improve next/image mock in Jest setup to handle boolean props correctly
- Enhance pre-push hook with better Docker detection and error handling
- Make Docker build test non-blocking (warnings instead of errors)
- Add executable permissions for secret check script
- Prevent React DOM warnings in tests
This commit is contained in:
2025-09-12 23:34:11 +02:00
parent 83705af7f6
commit 7f6694622c
3 changed files with 24 additions and 11 deletions

View File

@@ -99,6 +99,7 @@ fi
# Check for secrets in code
print_status "Checking for secrets in code..."
if [ -f "scripts/check-secrets.sh" ]; then
chmod +x scripts/check-secrets.sh
if ./scripts/check-secrets.sh; then
print_success "No secrets found in code"
else
@@ -138,14 +139,20 @@ if [ "$CURRENT_BRANCH" = "production" ]; then
print_warning "No .env file found. Make sure secrets are configured in Gitea."
fi
# Check Docker image can be built
print_status "Testing Docker build..."
if docker build -t portfolio-app:test . > /dev/null 2>&1; then
print_success "Docker build test passed"
docker rmi portfolio-app:test > /dev/null 2>&1
# Check if Docker is running
if ! docker info > /dev/null 2>&1; then
print_warning "Docker is not running. Skipping Docker build test."
else
print_error "Docker build test failed!"
exit 1
# Check Docker image can be built
print_status "Testing Docker build..."
if docker build -t portfolio-app:test . > /dev/null 2>&1; then
print_success "Docker build test passed"
docker rmi portfolio-app:test > /dev/null 2>&1
else
print_warning "Docker build test failed, but continuing..."
# Don't fail the push for Docker build issues in pre-push hook
# The CI/CD pipeline will catch this
fi
fi
fi