pear-engineering-workflow

To link a DevRev ticket to your Pear Commerce pull request, you must enforce mandatory DevRev ticket linking within the PR management workflow. This standardized practice ensures all code changes are tracked and meet team quality bars before merging.

Using git worktrees for concurrent Pear Commerce development involves creating isolated, non-conflicting edits across multiple repositories. This concurrent work management approach prevents tooling-related failures and keeps parallel feature branches cleanly separated.

To validate database changes safely before deploying Pear Commerce services, run real data checks using db.sh against the shared dev DB. This deploy safety rule ensures your modifications do not introduce production risk during code changes.

To verify a fix in api.pearcommerce.com before opening a pull request, use a dedicated codex/ worktree, run tests against the shared dev DB, and verify the fix with a live JSP probe. This ensures production-grade code review standards are met.

Yes, the Pear engineering workflow requires browser end-to-end testing for admin.pearcommerce.com to verify user-facing flows. This standardized testing eliminates inconsistent practices and reduces production risk during deployments.

PearEntity serialization rules are production-grade code review standards enforced during Pear engineering work. Following these rules ensures your code changes eliminate inconsistent practices and reduce production risk before deployment.