Back to Trust Center

Change Management Policy

Last Updated: January 9, 2026

Objective

To ensure that changes to the CandidateSeekers platform (code, infrastructure, configuration) are introduced in a controlled manner to minimize risk and ensure stability.

Development Workflow

We utilize a strict Git-based workflow for all code changes:

  1. Branching: Developers create feature branches from the main branch. Direct commits to `main` are prohibited.
  2. Testing: Changes are tested locally. Automated tests (linting, build checks) run on every push.
  3. Pull Requests (PR): A Pull Request is opened for review.
  4. Code Review: Another authorized reviewer (or automated approval controls for solo changes) must review the code for logic errors, security issues, and style compliance.
  5. Approval: The PR must be approved before merging.

Deployment Process

We utilize Vercel for Continuous Integration and Deployment (CI/CD).

  • Preview Environments: Every PR automatically deploys a preview environment for functional testing.
  • Production Deployment: Merging to the `main` branch triggers an automated deployment to Production.
  • Rollback: In case of critical failure, instant rollbacks are available via the Vercel dashboard.

Emergency Changes

Hotfixes for critical bugs (e.g., security vulnerabilities, site outages) may follow an expedited review process but must still pass automated build checks and be documented post-deployment.