If a repository keeps one branch per supported version or release, list those branches as maintained branches. CodeLynq then knows which lines are alive - so "all versions" means those branches, not every branch in the repository, including old versions and feature branches.
Set them up
- Open the project and go to its repositories.
- On the repository, under Maintained branches, click Choose branches (or Edit).
- Click the branches that are maintained. They are shown in version order (9.0 before 10.0).
- Click Save.
Choose what new tasks apply to
Once a repository has maintained branches, New tasks apply to offers two choices:
- the default branch - tasks use the default branch unless you choose branches on the task. This is how it works without maintained branches.
- all maintained branches - every new task starts with all maintained branches selected.
Either way, the choice is filled in on the task when it is created, so you see it - and can narrow or change it - in the task form, in the chat draft and on the task page. It applies to tasks created through the API and integrations as well.
Where maintained branches are used
- Task form: maintained branches are listed first under Branches, with All maintained to select them in one click.
- New-task chat: "all versions" or "every supported version" means the maintained branches. When you ask for a new version, the chat copies from the newest maintained branch.
- New branch: when adding a new branch, the newest maintained branch is suggested as the branch to copy from.
After an upgrade
When a task has created a new branch (for example 20.0) and opened its pull request, the repository shows CodeLynq created 20.0 for an upgrade. Maintain it from now on? Click Add 20.0 to make it a maintained branch. To stop maintaining an old version, edit the list and deselect it.
See also Work on several branches at once.