af-pr-preparation

Preparing a pull request involves verifying passing tests, linting, building, and updating documentation to meet defined exit criteria. This ensures code quality and confirms merge readiness before submitting a feature branch for review.

The pull request preparation process in CI/CD validates code against defined exit criteria, including passing tests, linting, and building. It integrates with the delivery workflow to ensure branch readiness before review and handoff.

You check if code meets PR exit criteria by running pre-submission checks that verify passing tests, successful builds, linting compliance, and required documentation updates. This confirms all mandatory review requirements are satisfied.

Yes, you need to update documentation before submitting a pull request to satisfy exit criteria. Documentation guidance ensures essential updates like README changes for new API details are completed, preventing delays in the review process.

The best way to ensure code quality before a pull request is to execute mandatory pre-submission checks, including tests, linting, and building. Verifying these automated checks and formatting standards prevents delays and ensures review readiness.

Your pull request fails merge readiness checks when mandatory exit criteria are unmet, such as failing tests, linting errors, build failures, or missing documentation updates. Completing these required checks ensures successful code review submission.