All 15 Git & Project Management questions
More in Git & Project Management
What is the purpose of a .gitignore file in a Node.js project, and what should always be included in it? What is the purpose of a CHANGELOG.md file in a Node.js project, and what should typically be included in each entry? What is a monorepo, and what specific tooling (like npm workspaces or Turborepo) helps manage multiple related Node.js packages within a single repository? What is semantic versioning (semver), and how does it inform how a Node.js package's version number should change between releases? What is the difference between npm, Yarn, and pnpm as Node.js package managers, and what specific advantage does pnpm offer regarding disk space? What is a pull request template, and how does it help standardize code review in a Node.js team's Git workflow? What is the purpose of an npm 'scripts' section in package.json, and how do custom scripts standardize common project tasks across a team? How would you use Git hooks (like a pre-commit hook via Husky) to enforce code quality checks before code is committed in a Node.js project? How would you structure conventional commit messages in a Node.js project, and how do they enable automated changelog generation? How would you use Git bisect to find the specific commit that introduced a regression in a Node.js application's behavior?
Advertisement
Node.js › Git & Project Management

How would you set up branch protection rules and required status checks for a Node.js repository to prevent broken code from being merged?

Intermediate

Answer

Branch protection rules (configured on the Git hosting platform, like GitHub) can require that a pull request pass specific CI checks (tests, linting, build) before it's allowed to merge, require at least one approving code review, and prevent direct pushes to the main branch entirely -- combined with a CI pipeline that runs these checks automatically on every pull request, this ensures broken or unreviewed code can't reach the main branch regardless of who's making the change.
# GitHub branch protection settings (conceptual, configured via the UI or API)
required_status_checks: ['test', 'lint', 'build']
required_approving_review_count: 1
enforce_admins: true
restrict_pushes: true # no direct pushes to main, only via pull request
Real-world example A team enables branch protection on their main branch requiring the CI test suite and linter to pass along with at least one code review approval, preventing an incident where a developer had previously pushed directly to main with a change that broke production.

Common follow-ups: Should branch protection rules apply equally to repository administrators, or is an exception sometimes justified?;How do you handle an urgent hotfix that needs to bypass the normal review process during an active incident?

CI/CD Publishing & Deployment;engineering:code-review
All 15 Git & Project Management questions