{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/80c3d419c2e846e5bc2b144327618e61\" frameborder=\"0\" width=\"2214\" height=\"1660\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1660,"width":2214,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1660,"thumbnail_width":2214,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/80c3d419c2e846e5bc2b144327618e61-da7796657c43a8c4-full.jpg","duration":374.976,"title":"Connecting your GitHub Repository to OPERATE","description":"Hey guys, I am Aditya Goudar from the operate team at Better, and today I walk you through connecting your GitHub or GitLab repository to operate for root cause analysis and other actions. You need three environment variables, a GitHub or GitLab personal access token, your repo owner, and your repo name, which you can inject via an ENB or tools like Doppler, AWS secrets manager, or any vault. I show how to create a classic personal access token with the right read and write scopes. After you refresh, GitHub should show as active, and I verify merged and open PRs and then ask the agent to open a PR on a new Docs branch. No extra action is requested, but you should set those three variables and test it."}