{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/63963d2092614920815f53f02747755e\" frameborder=\"0\" width=\"1114\" height=\"835\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":835,"width":1114,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":835,"thumbnail_width":1114,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/63963d2092614920815f53f02747755e-3ceb713ad5dc6e19-full.jpg","duration":237.816,"title":"Automating Technical Documentation using Cubyts","description":"In this video, I walk you through how Qubits automatically generates technical documentation after a pull request is merged, ensuring consistency and governance in our documentation process. The technical documentation captures essential details such as architecture, API changes, and operational considerations, all linked to the specific pull request for traceability. We utilize flags to enforce documentation generation, which operates under the auto-resolution mechanism, ensuring that documentation is always complete and stored in expected locations like GitHub or Jira. I encourage you to review the generated documentation for each merge to ensure alignment with our code changes. Thank you for your attention to this important aspect of our development process."}