This directory contains automated workflows for the iAgent project.
- Triggers: Push to
main
/develop
, Pull Requests tomain
- Purpose: Code quality checks, testing, and build verification
- Jobs:
- 🧹 Quality: ESLint + TypeScript checking
- 🧪 Test: Unit tests with coverage
- 🏗️ Build: Production build verification
- 🔒 Security: npm audit security scan
- Triggers: Push to
main
(after CI), Manual dispatch - Purpose: Deploy frontend to GitHub Pages
- Features:
- ✅ Production build with optimizations
- 🔧 Automatic GitHub Pages configuration
- 🌐 Deployment verification
- 📊 Build size analysis
- Push changes to
main
branch - CI workflow runs automatically
- If CI passes, GitHub Pages deployment starts
- Frontend is built and deployed to:
https://<username>.github.io/iagent/
# Local deployment (requires gh-pages CLI)
npm run deploy:local
# Or trigger GitHub Actions manually
gh workflow run deploy-gh-pages.yml
The workflows use these environment variables for GitHub Pages:
VITE_BASE_URL
:/iagent/
(GitHub Pages subdirectory)VITE_API_BASE_URL
:/iagent/api/
(API endpoint path)VITE_ENVIRONMENT
:production
- Go to repository Settings → Pages
- Set Source to "GitHub Actions"
- The workflow will handle deployment automatically
You can monitor workflow runs in the Actions tab of your repository:
- ✅ Green checkmark: All jobs passed
- ❌ Red X: Some jobs failed
- 🟡 Yellow dot: In progress
- ⚪ Gray dot: Not run
Build Fails
- Check TypeScript errors in CI logs
- Ensure all dependencies are properly installed
- Verify environment variables are set correctly
Deployment Fails
- Check GitHub Pages settings are configured
- Verify repository has Pages enabled
- Ensure workflows have proper permissions
Tests Fail
- Review test output in CI logs
- Check if all test dependencies are available
- Verify test environment setup
- Check the Actions tab for detailed logs
- Review the specific job that failed
- Look for error messages in the workflow output
- Check if the issue is related to dependencies or configuration