# Custom Script Manifest Files

## Overview

Adding your own script manifest file will enable you to test any custom SQL that you have written and also run any SQL code on the schedule you create as part of a workflow

The Daasity platform uses the script manifest file to determine what SQL code should be executed.    For more information on script manifest files read the [Daasity Script Manifest File](https://help.daasity.com/technical-docs/workflows-and-scheduling/script-manifest-yaml-files) article 

Before you create your custom script manifest file you should have completed the following steps:

1. [Gotten access to your Code Repository](https://help.daasity.com/technical-docs/transform-code/code-repository/getting-access-to-your-code-repository)
2. [Learned how to manage branches in Github](https://help.daasity.com/technical-docs/transform-code/code-repository/code-repository-branches)
3. [Written custom SQL code](https://help.daasity.com/technical-docs/transform-code/code-repository/custom-sql-code)

## Creating a Custom Script Manifest File

With a development branch created simply open your text editor to create your custom script manifest file.  You can use the text below \[`test_demo.yml`] to create a script manifest file that will execute the \[`test_demo.sql`] file created in the [Custom SQL Code](https://help.daasity.com/technical-docs/transform-code/code-repository/custom-sql-code) article

<pre><code># ----------------------------------------------------------------
# Test YML
<strong># ----------------------------------------------------------------
</strong>
version:  '2.0.0'

sections:
  test:
    scripts:
      - "demo_test.sql"
</code></pre>

<figure><img src="https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/ic27CEu085vvEQdLMsjY/image.png" alt=""><figcaption></figcaption></figure>

Save this as a .yml file in the local repository

<figure><img src="https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/HlPxrJCOzWvKM8LqoUia/Screenshot%202023-07-11%20at%209.59.17%20AM.png" alt=""><figcaption></figcaption></figure>

You then need to push the script manifest file to Github to make the file available to the Daasity App to execute

## Pushing Script Manifest Files to Github

First you will need to commit the changes you have made by giving the change a name and description (optional)

<figure><img src="https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/J2qPCP0N54twaC1pADGX/image.png" alt=""><figcaption></figcaption></figure>

Then you will need to push the changes to the remote repository

<figure><img src="https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/KDObPYMZLDo49DyicBg1/image.png" alt=""><figcaption></figcaption></figure>

From here you have several options:

1. Create a test warehouse that will allow you to run your script manifest file on a duplicate version of your data warehouse
2. Create a pull request to merge your changes into the master branch so the script manifest file is available in production