> ## Documentation Index > Fetch the complete documentation index at: https://docs.codeobsess.com/llms.txt > Use this file to discover all available pages before exploring further. # Pull requests > How CodeObsess opens and updates pull requests, and how review comments reach it. ## What CodeObsess does * It pushes its own branch, named `codeobsess/-`, and opens a pull request. * The pull request is assigned to the person who asked, when their account is linked, and its commits name them as co-author. * A follow-up on the same ticket updates the same open pull request. * If its review could not run, or a problem remains, the pull request is a draft. * If a ticket changes several repositories, each gets its own pull request, and each lists the others in the order to merge them. * It never merges, never force-pushes, and never makes releases or tags. ## Pull requests in CodeObsess **Pull requests** lists every pull request CodeObsess opened, with its state and when it was created. Click a row to open it. You can filter by person, product or repository. ![The Pull requests page listing pull requests with repository, state and created time](https://mintcdn.com/code-obsess/0ZvNNm_XHMri9byY/images/tickets/pull-requests-light.png?fit=max\&auto=format\&n=0ZvNNm_XHMri9byY\&q=85\&s=95c25db33fe4f017745d951f99bd31e2) ## Review comments A review on a CodeObsess pull request doesn't start a run by itself. CodeObsess posts it into the ticket. The person who asked replies in the ticket to start one round of fixes, on their own AI. ## Tests not run If a pull request lists tests as not run, CodeObsess couldn't run them in its space. Run them yourself before you merge. ## Merging You review and merge. CodeObsess never waits on your CI. If you want it to react to a CI failure, reply in the ticket with what failed. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.