Features
Versioning
Versioning
Each unique state of a remote configuration is saved as a different version in Orquesta. This allows you to track changes over time and rollback to previous configurations if necessary.
The goal of version control is to be able to keep track and manage changes to the prompts or remote configuration over time, this helps prompt engineers and prompt managers maintain a historical record of every modification made to a prompt or remote configuration and also enable them navigate through different versions.
Versions are usually numbered sequentially and may also include metadata like who made changes and when (date and time the changes occur). Orquesta helps to keep track of these changes by adding labels to each version, your current working version is labelled Current .
To access the version control on the Orquesta dashboard, you will locate the clock icon and click on it as shown in the image below.
On clicking on the icon, you will see all the different versions you have created while working on the prompt in Orquesta, each prompt is saved as a new version whenever you click on the Publish button.
The process of reverting to a previous version of a remote configuration is called Rollback. To Rollback to a specific version, all you have to do it click on the version you want to Rollback and click on the Rollback button on the dashboard, and the prompt version is restored.
Wrap up
Version control plays a crucial role in maintaining the integrity and consistency of the prompt and remote configuration, as it helps to track changes made to the prompts over time, If a change is made to a prompt that later turns out to be a mistake, version control allows you to easily revert back to a previous version of the prompt. Finally, it helps teams to collaborate better and perform experimentation.
Get started today.
Check out Orquesta documentation.
Versioning
Each unique state of a remote configuration is saved as a different version in Orquesta. This allows you to track changes over time and rollback to previous configurations if necessary.
The goal of version control is to be able to keep track and manage changes to the prompts or remote configuration over time, this helps prompt engineers and prompt managers maintain a historical record of every modification made to a prompt or remote configuration and also enable them navigate through different versions.
Versions are usually numbered sequentially and may also include metadata like who made changes and when (date and time the changes occur). Orquesta helps to keep track of these changes by adding labels to each version, your current working version is labelled Current .
To access the version control on the Orquesta dashboard, you will locate the clock icon and click on it as shown in the image below.
On clicking on the icon, you will see all the different versions you have created while working on the prompt in Orquesta, each prompt is saved as a new version whenever you click on the Publish button.
The process of reverting to a previous version of a remote configuration is called Rollback. To Rollback to a specific version, all you have to do it click on the version you want to Rollback and click on the Rollback button on the dashboard, and the prompt version is restored.
Wrap up
Version control plays a crucial role in maintaining the integrity and consistency of the prompt and remote configuration, as it helps to track changes made to the prompts over time, If a change is made to a prompt that later turns out to be a mistake, version control allows you to easily revert back to a previous version of the prompt. Finally, it helps teams to collaborate better and perform experimentation.
Get started today.
Check out Orquesta documentation.
Versioning
Each unique state of a remote configuration is saved as a different version in Orquesta. This allows you to track changes over time and rollback to previous configurations if necessary.
The goal of version control is to be able to keep track and manage changes to the prompts or remote configuration over time, this helps prompt engineers and prompt managers maintain a historical record of every modification made to a prompt or remote configuration and also enable them navigate through different versions.
Versions are usually numbered sequentially and may also include metadata like who made changes and when (date and time the changes occur). Orquesta helps to keep track of these changes by adding labels to each version, your current working version is labelled Current .
To access the version control on the Orquesta dashboard, you will locate the clock icon and click on it as shown in the image below.
On clicking on the icon, you will see all the different versions you have created while working on the prompt in Orquesta, each prompt is saved as a new version whenever you click on the Publish button.
The process of reverting to a previous version of a remote configuration is called Rollback. To Rollback to a specific version, all you have to do it click on the version you want to Rollback and click on the Rollback button on the dashboard, and the prompt version is restored.
Wrap up
Version control plays a crucial role in maintaining the integrity and consistency of the prompt and remote configuration, as it helps to track changes made to the prompts over time, If a change is made to a prompt that later turns out to be a mistake, version control allows you to easily revert back to a previous version of the prompt. Finally, it helps teams to collaborate better and perform experimentation.
Get started today.
Check out Orquesta documentation.
