GitHub Actions

Prerequisite

The .yml must exist in the main branch of your GitHub repository.

Generate Personal Authentication Token

Follow these steps to create a personal access token in GitHub:

  1. Log in to GitHub.

  2. Open your User Profile, then go to Settings.

  3. In the left navigation pane, select Developer Settings.

  4. Click Tokens (classic).

  5. Click Generate new token.

    GitHub Developer Settings page showing the Personal access tokens (classic) section with an option highlighted to Generate new token for creating a new authentication token.

  6. Define the Scopes to grant access to the token, then generate it.

    GitHub Personal access tokens (classic) page showing a newly generated token highlighted in green with a reminder to copy it immediately, as it will not be visible again later.

  7. Copy and store the generated token securely.

Construct the URL

Use the following format to construct the GitHub Actions API URL for triggering a build:

https://api.github.com/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches

Placeholder values:

  • owner: GitHub username or organization name (for example, Lizamathew)

  • repo: Repository name (for example, parameter)

  • workflow_id: Workflow ID or file name (for example, 54649623)

Example URL:

https://api.github.com/repos/Lizamathew/parameter/actions/workflows/54649623/dispatches

CI/CD Rule Configuration in QTM

The following are examples of triggering the build without parameters and with query parameters.

CI/CD Rule Without Query Parameters

CI/CD rule configuration for “GitHub Actions QTM” displaying a webhook URL, masked Authorization header, POST method, and webhook body set to NONE with no query parameters defined.

CI/CD Rule With RAW Parameters

CI/CD rule configuration screen for “GitHub Actions QTM” showing a webhook URL, masked Authorization header, POST method, and RAW webhook body format with masked JSON content.
In this section:
© 2025
Publication date: