1. Home
  2. Knowledge Base
  3. HappyPress
  4. Git Mirroring
  5. Merge Request Communications and SLAs

Merge Request Communications and SLAs

If you have Git Mirroring enabled with your HappyPress subscription, that’ll be because you want the power to enhance your site with your own code. And while we have high standards in terms of code quality, we don’t want to provide any unnecessary obstacles, particularly where comms is concerned.

Upon submitting a merge request, you should expect a speedy response from our team and a full review of your code shortly afterwards.

  • Our operations team aims to provide an initial confirmation within one working day of receiving your MR.
  • Our development team aims to provide a code review within two working days of receiving your MR.

Please assign a member of our ops teams to your merge request in order to ensure that it is triaged in line with the target SLAs listed above. If you do not know who your ops contact is, please get in touch via live chat and we’ll be happy to point you in the right direction.

The code review will conclude with one of two outcomes:

  1. The MR is acceptable and we can arrange a time frame for merging your work into production
  2. The MR needs amendments or improvements. In these cases, we aim to provide as clear and concise an explanation as possible.

Any further comments made on the MR thread are subject to our one working day SLA for comms and any further merge requests themselves are subject to our two working days SLA for code review.

Learn more about preparing a successful merge request.

Updated on September 1, 2022

Was this article helpful?

Related Articles

Not the solution you were looking for?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support