Neo | DocsAssign a ticket
Just assign a ticket to Neo, and it will leave a comment saying “I’m on it” to confirm it has begun work as a coder.
When done, Neo will leave another comment with a link to the PR it has created or updated, or to the branch it has updated - see Branch names for details.
What to put on the ticket
Neo reads the title, description and comments of the ticket you assign to it, as well as any of its ancestor tickets.
-
Describe the task as you would for a teammate, including what to do in edge cases
-
Mention names of classes or files that might be relevant
-
Link to or attach References , such as a PDF or word document with a product specification
-
Embed or attach Images, such as screenshots of a user interface, or a class diagram
Give Neo tasks that are moderate in size, break it into subtasks if it is large. See Workflows for coding with Neo.
Retrying a ticket
The usual workflow is to leave comments on Neo’s PR. But sometimes Neo’s approach to solving the ticket is very different from what you wanted, and it is best to restart.
First tweak the specification a little, providing some more detail. Add a link to documentation or a hint about which class Neo should modify.
When you’re ready, @ mention Neo telling it to “try again”. Or, if you prefer, unassign the ticket and reassign it.
⚠️ In some tools, like AzureDevOps, you need to un-assign, save the ticket, then assign again, or the tool won’t register the change and Neo won’t be notified.
Neo will make a new pull request, and you can close the old one.