> For the complete documentation index, see [llms.txt](https://docs.winga.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.winga.me/import-guides/importing-from-github.md).

# Importing from GitHub

Winga can read a repository's GitHub Actions secrets and variables and turn them into feature flags. This guide covers connecting GitHub to your workspace and running the import.

***

### 1. Connect GitHub

Open your workspace and go to **Connections** from the workspace navigation. On the Connections page, find the **GitHub** card under *Available integrations* and press **Connect**.

GitHub connects through **OAuth**. A short pre-flight dialog reminds you to make sure you're signed into the correct GitHub account at `github.com` before continuing, then redirects you to GitHub to authorize the connection. After you approve, GitHub returns you to Winga and you confirm which account was connected. You need the **owner** or **admin** role in the workspace to add or remove a connection.

***

### 2. Start the import

The import wizard lives on a project's **Flags** page. Open the project you want to import into, go to its **Flags** page, and start an import. Choose **Import from GitHub**, then pick the repository to import from.

***

### 3. How secrets and variables are partitioned

GitHub Actions has two kinds of configuration, and Winga handles them differently:

* **Actions variables** import **with their values**. GitHub exposes both the name and value of a variable through its API.
* **Actions secrets** import as **name only**. GitHub never returns a secret's value through its API — only its name — so Winga imports the key with an empty value. You set the real value yourself after the flag is created.

Because of this split, the **Import values too** option in the configure step is only available when the repository has at least one Actions variable. A repository with only secrets imports the names so you can recreate the flags, and you fill in values manually.

***

### 4. Review and configure

After the variables are fetched, the review step lists every key. Deselect any you don't want, then move to the configure step to:

* choose which environments the imported flags are enabled in, and
* optionally import the parsed values as flag defaults (off by default — only enable this for test or example values, never production secrets).

Press **Import** to create the flags.