CHECK IN PROCESS FOR PULL REQUESTS

Development Process

Effective Date: January 1, 2023

  1. Before any significant code changes are made, the developer must create a new branch for their work.
  2. The developer must then thoroughly test their code changes to ensure that they do not introduce any bugs or errors.
  3. Once the code changes have been tested, the developer must submit a pull request for review.
  4. The pull request should include a detailed description of the changes made, as well as any potential impacts on existing code or systems.
  5. The pull request should be assigned to at least one reviewer, who will be responsible for reviewing the code changes and providing feedback.
  6. The reviewer(s) should thoroughly test the code changes and provide feedback to the developer.
  7. If the code changes require significant changes or if there are concerns about the impact on existing code or systems, the pull request should be escalated to the director of engineering.
  8. The director of engineering will review the code changes and provide final approval or request further changes.
  9. Once the code changes have been approved, they can be merged into the production branch.

By following this Check In Process, we can ensure that significant code changes are thoroughly tested and reviewed before they are merged into any production branch. This helps to prevent any potential issues or errors from being introduced into our systems and ensures that all code changes are made with the necessary oversight and approval.

‍