Skip to content

chore(ci): improve CI/CD pipeline with security scanning, coverage, and deployment - #49

Closed
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1770118446-improve-ci-cd-pipeline
Closed

devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1770118446-improve-ci-cd-pipeline

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Feb 3, 2026 •

Copy link
Copy Markdown

What does this PR do?

This PR improves the CI/CD pipeline for cal.com by adding security scanning, code coverage reporting, automated dependency updates, and a staging deployment workflow.

Changes:

  • Fix lint workflow: Removed continue-on-error: true so lint failures now properly fail the build
  • Add Dependabot: Configured automated dependency updates for npm packages and GitHub Actions (weekly, grouped by minor/patch)
  • Add CodeQL security scanning: SAST analysis for JavaScript/TypeScript on PRs, pushes to main, and weekly schedule
  • Add code coverage: Unit tests now generate and upload coverage reports as artifacts
  • Enable integration test uploads: Uncommented the TODO for uploading integration test results
  • Add staging deployment workflow: Builds Docker image and pushes to GHCR on main branch pushes

Requested by: kiran-6.kumar-6@cognizant.com

Link to Devin run: https://partner-workshops.devinenterprise.com/sessions/6706d2aece5a4c2aa9779a451675de1d

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A - CI/CD changes only.
  • I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

  1. Lint workflow: Create a PR with a lint error and verify the CI fails (previously it would pass with continue-on-error: true)
  2. Dependabot: After merge, check that Dependabot creates PRs for dependency updates on the next scheduled run (Monday 09:00 UTC)
  3. CodeQL: Verify the CodeQL workflow runs on this PR and subsequent PRs to main
  4. Coverage: Check that the coverage-report artifact is uploaded after unit tests run
  5. Staging deployment: After merge to main, verify the Docker image is built and pushed to GHCR

Environment variables needed for staging deployment:

  • STAGING_WEBAPP_URL (repository variable)
  • STAGING_API_V2_URL (repository variable)

Checklist for Human Reviewers

  • Verify removing continue-on-error: true from lint won't break existing workflows (check if codebase currently passes lint)
  • Confirm the staging deployment workflow meets requirements - note it only builds/pushes Docker images to GHCR, it does NOT deploy to actual infrastructure
  • Review Dependabot configuration - currently ignores major version updates, groups minor/patch together
  • Verify CodeQL query sets (security-extended,security-and-quality) are appropriate for the project

…nd deployment

- Fix lint workflow: Remove continue-on-error to properly fail on lint errors
- Add Dependabot configuration for automated dependency updates (npm and GitHub Actions)
- Add CodeQL security analysis workflow for JavaScript/TypeScript SAST
- Enhance unit tests with coverage reporting and artifact uploads
- Enable integration test result uploads (previously commented out as TODO)
- Add staging deployment workflow with Docker image build and push to GHCR
@devin-ai-integration

Copy link
Copy Markdown
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@devin-ai-integration
devin-ai-integration Bot deleted the devin/1770118446-improve-ci-cd-pipeline branch April 24, 2026 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants