Skip to main content

What CodeObsess does

  • It pushes its own branch, named codeobsess/<ticket>-<short-name>, 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 timeThe Pull requests page listing pull requests with repository, state and created time

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.