> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/mergequeue/concepts/affected-targets/github-actions-based-affected-targets.md).

# GitHub Actions based Affected Targets

Learn how to configure GitHub Actions workflows to run only when certain files are changed. MergeQueue can identify the affected targets for the queue.

You can configure GitHub Actions workflows to run only when certain files are changed.

```yaml
on:
  push:
    paths:
      - '**.js'
```

Aviator MergeQueue can interpret this config to identify affected targets for the queue.

## Setup

In order to use GitHub Actions workflow to identify the affected targets, you need to create a new GitHub Actions workflow by using [<mark style="color:blue;">aviator-co/affected-targets-gha-action</mark>](https://github.com/aviator-co/affected-targets-gha-action).

Create following GHA workflow config.

```yaml
name: aviator-affected-targets

on:
  pull_request:

jobs:
  aviator-affected-targets:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: aviator-co/affected-targets-gha-action@v1
        with:
          aviator-token: ${{ secrets.AVIATOR_TOKEN }}
```

You can get the Aviator API token from [<mark style="color:blue;">https://app.aviator.co/settings/workspace/integrations</mark>](https://app.aviator.co/settings/workspace/integrations) and store it as a GitHub Actions secret.

Every time a PR is created, this workflow runs and detect which workflow is affected. This is sent to Aviator, and when this PR gets queued, it uses the affected targets reported by this action.


---

# 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.aviator.co/mergequeue/concepts/affected-targets/github-actions-based-affected-targets.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.