Too Long; Didn't Read
Octopus's Configuration as Code feature lets you store your deployment process as configuration files in a Git repository rather than in the Octopus database. The configuration is stored as human-readable files that use Octopus Configuration Language (OCL) This arrangement makes it easy to find the appropriate deployment process for each application. We recommend keeping your configuration in the same repository as the application code, but there are specific circumstances where the other options may be suitable. If you don't want changes to the deployment process to trigger a build of your application, you can mask the `octopus` folder in your build.