Merge Pr

Summary

PRs are merged by the same individual that submitted the PR

Prerequisites

• Have maintain permission in Dendron repo (everyone in Engineering (Private) gets this)
• Have your PR approved by either @kevin (Private) or @jonathan (Private) and all outstanding discussions resolved

Steps

1. Merge PR
   • when merging PR, make sure the commit message corresponds to our commit style
   • eg. enhance(publish): speed up publishing by 500%
2. Move the commit to ready to ship

   No note with name area.product.sop.ready-to-ship found in cache during parsing.

3. Create Analytics (Private) entries in the proper release version
4. If the change is going out in the current release, merge in any doc changes. Otherwise, create a task to merge in docs after the current release is pushed

Related

• Ready to Ship (Private)

---

Backlinks

• Changelog
• Submitting Code for Review