Branch names
Neo automatically works out what to call the branch for its PR, and whether to base it on an existing branch (e.g. a feature branch).
How Neo chooses branch names
Neo looks at existing branches and pull requests, and will use those to help work out how your team names branches.
You can give specific instructions on a ticket saying what branch you’d like Neo to base its PR off, or what it should call the new branch.
If the ticket assigned to Neo is a subtask or a story, you can put instructions in the parent ticket. For example, this is a good place to name a feature branch.
Customising branch rules to your team
If Neo’s default behaviour isn’t quite right for your team, then you can point Neo to your team documentation on naming branches, making feature branches and so on.
To do this, add documents with appropriate instructions about branching to Neo’s Context documents.
Other options for where Neo codes
Usuaully Neo will make a new branch (or branches) and a new PR. It’s less common, and you will need to tell Neo explicitly, but you can also get Neo to:
-
Update an existing PR. It’s better to just leave a comment for Neo on the PR, see Comment on a PR.
-
Push a commit to an existing branch. You’ll have to be really clear and specific in the ticket to get Neo to do this.