From be7852cd20204f10d20634c5ea2b897289496497 Mon Sep 17 00:00:00 2001 From: Dominik Jain Date: Mon, 2 Jun 2025 17:19:43 +0200 Subject: [PATCH] Update instructions pertaining to managed list of projects --- serena_config.template.yml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/serena_config.template.yml b/serena_config.template.yml index 269c01f8..33a9cd3b 100644 --- a/serena_config.template.yml +++ b/serena_config.template.yml @@ -24,11 +24,13 @@ gui_log_level: 20 # minimum log level for the GUI log window (10 = debug, 20 = info, 30 = warning, 40 = error) -# The list of registered projects (which you can switch between using "activate_project"). -# MANAGED BY SERENA, KEEP AT THE BOTTOM OF THE YAML AND DON'T ADJUST WITHOUT NEED (you may add paths though) -# Whenever a project is activated (either by using the tool or by starting the server with --project), -# the project's path will be added here and you will be able to activate it by its name in the future. +# MANAGED BY SERENA, KEEP AT THE BOTTOM OF THE YAML AND DON'T EDIT WITHOUT NEED +# The list of registered projects. +# To add a project, within a chat, simply ask Serena to "activate the project /path/to/project" or, +# if the project was previously added, "activate the project ". # By default, the project's name will be the name of the directory containing the project, but you may change it -# by changing the entry in the (autogenerated) `.serena/project.yml` file. -# Note: make sure there are no name collisions in the names of registered projects +# by editing the (auto-generated) project configuration file `/path/project/project/.serena/project.yml` file. +# If you want to maintain full control of the project configuration, create the project.yml file manually and then +# instruct Serena to activate the project by its path for first-time activation. +# NOTE: Make sure there are no name collisions in the names of registered projects. projects: []