> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/feature-management-experimentation/management-and-administration/integrations/github-actions.md).

# GitHub Actions

### Feature Flags Evaluator GitHub Action <a href="#feature-flags-evaluator-github-action" id="feature-flags-evaluator-github-action"></a>

[GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions) is a continuous integration and continuous delivery (CI/CD) platform. GitHub Actions allows you to trigger workflows that execute a series of commands on your GitHub repository files.

The Split Feature Flags Evaluator Github Action integrates the Harness FME SDK into your existing GitHub workflows. This GitHub Action uses the [Harness FME Node.js SDK](/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/server-side-sdks/nodejs-sdk.md) to evaluate feature flags and outputs the feature flag treatment results for use later in the workflow.

The [Split Feature Flags Evaluator GitHub Action](https://github.com/marketplace/actions/split-software-feature-flags-evaluator) is a community-supported integration. We do our best to ensure that we share only high-quality community integrations and solutions but we do not work on these projects directly, nor can we guarantee that they’re consistently maintained.

### How it works <a href="#how-it-works" id="how-it-works"></a>

GitHub workflows are triggered by events on your repository, like a merge into the main branch. A GitHub workflow step can run the Split Feature Flag Evaluator GitHub Action and make the feature flag evaluation results available to other workflow steps and jobs. This allows you to refine your CI/CD processes using Harness FME feature flags.

### Setting up the Split Feature Flags Evaluator <a href="#setting-up-the-split-feature-flags-evaluator" id="setting-up-the-split-feature-flags-evaluator"></a>

#### In Harness FME <a href="#in-harness-fme" id="in-harness-fme"></a>

In the Harness FME, you first need to create your feature flags. Take note of the FME environment for which you create your feature flag targeting rules. In **FME Settings**, find the *server-side SDK API Key* for this environment and store it as a GitHub [secret](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) for use in your GitHub workflow.

#### In a GitHub workflow <a href="#in-a-github-workflow" id="in-a-github-workflow"></a>

To learn how to integrate the Split Feature Flags Evaluator into a GitHub workflow, see [Split Software: Feature Flags Evaluator](https://github.com/marketplace/actions/split-software-feature-flags-evaluator) in GitHub Marketplace.

### About this integration <a href="#about-this-integration" id="about-this-integration"></a>

This is a third-party integration that has been tested by the Harness FME team. Harness does not own or maintain this integration. For more information, contact the [contributor](mailto:sebastian.arrubia@split.io).

If you’d like a demo of Harness FME or need help implementing any of our integrations, contact <support@split.io>.