> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/1-8-0/documentation/workbench/flows-in-git-repositories.md).

# Flows in Git Repositories

The Workbench allows to store Flows in any external Git Repository. This is called the “Workbench Projects” feature.

You can get familiar with Node-RED’s Projects feature (<https://nodered.org/docs/user-guide/projects/>) to understand how this works in practice. In order to enable it in your Connectware, you must modify the configuration as described next.

## Configuration

In order to enable the *workbench projects* feature, the following [Environment Variables](/1-8-0/documentation/configuration/environment-variables.md) must be configured:

* **CYBUS\_WORKBENCH\_PROJECTS\_ENABLED:** If *true*, the Projects feature will be enabled. Default: *false*.

If the feature should be enabled, this value needs to be set to *true* in the environment variable configuration. By default the settings should look like this:

{% code lineNumbers="true" %}

```yaml
# Workbench Configuration
CYBUS_WORKBENCH_PROJECTS_ENABLED=false
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/1-8-0/documentation/workbench/flows-in-git-repositories.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.