Customizing Neo Coder

💡 Many of these customizatoins involve editing Neo’s “context documents”. There are configured by your Neo administrator, and are documents in your team’s document manager (e.g. Confluence, Notion, Google Docs). You can ask them which documents Neo has, and edit them yourself.

Code style guidelines

Neo will stay consistent with coding styles of your codebase where it can.

If you have a code style guidelines document for your project or company, ask your administrator to add it to Neo’s Context documents.

If you spot Neo making a consistent mistake in coding style, it is worth adding it yourself to Neo’s Context documents.

Directory layout of code

Neo tries its best to find where things are in your codebase, but sometimes you might notice it struggling with certain directories, or putting files in the wrong place consistently.

In that case, add information about the directory structure or file location to Neo’s Context documents.

Commit messages

Some teams have rules for format of commit messages. You can specify these in Neo’s Context documents.

Pull request templates

Neo will automatically write pull request decriptions in the format you’ve configured in your tool.

The exact name depends on which code repository you use, and how you’ve set up your project. Neo will find files like pull_request_template.md, and directories like PULL_REQUEST_TEMPLATE or merge_request_templates.

⚠️ Neo doesn’t support this feature for Bitbucket, because it doesn’t use files in the repository for PR templates. Please Contact Support if this is important to you.

Draft pull requests