github.d.ts

/* eslint-disable */
/**
 * This file was automatically generated by json-schema-to-typescript.
 * DO NOT MODIFY IT BY HAND. Instead, modify the source JSONSchema file,
 * and run json-schema-to-typescript to regenerate this file.
 */

export type Event =
  | "branch_protection_rule"
  | "check_run"
  | "check_suite"
  | "create"
  | "delete"
  | "deployment"
  | "deployment_status"
  | "discussion"
  | "discussion_comment"
  | "fork"
  | "gollum"
  | "issue_comment"
  | "issues"
  | "label"
  | "member"
  | "milestone"
  | "page_build"
  | "project"
  | "project_card"
  | "project_column"
  | "public"
  | "pull_request"
  | "pull_request_review"
  | "pull_request_review_comment"
  | "pull_request_target"
  | "push"
  | "registry_package"
  | "release"
  | "status"
  | "watch"
  | "workflow_call"
  | "workflow_dispatch"
  | "workflow_run"
  | "repository_dispatch";
/**
 * Runs your workflow anytime the branch_protection_rule event occurs. More than one activity type triggers this event.
 */
export type EventObject = {
  types?: Types;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types = [
  "created" | "edited" | "deleted",
  ...("created" | "edited" | "deleted")[],
];
/**
 * Runs your workflow anytime the check_run event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/checks/runs.
 */
export type EventObject1 = {
  types?: Types1;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types1 = [
  "created" | "rerequested" | "completed" | "requested_action",
  ...("created" | "rerequested" | "completed" | "requested_action")[],
];
/**
 * Runs your workflow anytime the check_suite event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/checks/suites/.
 */
export type EventObject2 = {
  types?: Types2;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types2 = [
  "completed" | "requested" | "rerequested",
  ...("completed" | "requested" | "rerequested")[],
];
/**
 * Runs your workflow anytime the discussion event occurs. More than one activity type triggers this event. For information about the GraphQL API, see https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions
 */
export type EventObject3 = {
  types?: Types3;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types3 = [
  (
    | "created"
    | "edited"
    | "deleted"
    | "transferred"
    | "pinned"
    | "unpinned"
    | "labeled"
    | "unlabeled"
    | "locked"
    | "unlocked"
    | "category_changed"
    | "answered"
    | "unanswered"
  ),
  ...(
    | "created"
    | "edited"
    | "deleted"
    | "transferred"
    | "pinned"
    | "unpinned"
    | "labeled"
    | "unlabeled"
    | "locked"
    | "unlocked"
    | "category_changed"
    | "answered"
    | "unanswered"
  )[],
];
/**
 * Runs your workflow anytime the discussion_comment event occurs. More than one activity type triggers this event. For information about the GraphQL API, see https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions
 */
export type EventObject4 = {
  types?: Types4;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types4 = [
  "created" | "edited" | "deleted",
  ...("created" | "edited" | "deleted")[],
];
/**
 * Runs your workflow anytime the issue_comment event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues/comments/.
 */
export type EventObject5 = {
  types?: Types5;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types5 = [
  "created" | "edited" | "deleted",
  ...("created" | "edited" | "deleted")[],
];
/**
 * Runs your workflow anytime the issues event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues.
 */
export type EventObject6 = {
  types?: Types6;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types6 = [
  (
    | "opened"
    | "edited"
    | "deleted"
    | "transferred"
    | "pinned"
    | "unpinned"
    | "closed"
    | "reopened"
    | "assigned"
    | "unassigned"
    | "labeled"
    | "unlabeled"
    | "locked"
    | "unlocked"
    | "milestoned"
    | "demilestoned"
  ),
  ...(
    | "opened"
    | "edited"
    | "deleted"
    | "transferred"
    | "pinned"
    | "unpinned"
    | "closed"
    | "reopened"
    | "assigned"
    | "unassigned"
    | "labeled"
    | "unlabeled"
    | "locked"
    | "unlocked"
    | "milestoned"
    | "demilestoned"
  )[],
];
/**
 * Runs your workflow anytime the label event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues/labels/.
 */
export type EventObject7 = {
  types?: Types7;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types7 = [
  "created" | "edited" | "deleted",
  ...("created" | "edited" | "deleted")[],
];
/**
 * Runs your workflow anytime the member event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/repos/collaborators/.
 */
export type EventObject8 = {
  types?: Types8;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types8 = [
  "added" | "edited" | "deleted",
  ...("added" | "edited" | "deleted")[],
];
/**
 * Runs your workflow when a pull request is added to a merge queue, which adds the pull request to a merge group. For information about the merge queue, see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue .
 */
export type EventObject9 = {
  types?: Types9;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types9 = ["checks_requested", ..."checks_requested"[]];
/**
 * Runs your workflow anytime the milestone event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues/milestones/.
 */
export type EventObject10 = {
  types?: Types10;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types10 = [
  "created" | "closed" | "opened" | "edited" | "deleted",
  ...("created" | "closed" | "opened" | "edited" | "deleted")[],
];
/**
 * Runs your workflow anytime the project event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/projects/.
 */
export type EventObject11 = {
  types?: Types11;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types11 = [
  "created" | "updated" | "closed" | "reopened" | "edited" | "deleted",
  ...("created" | "updated" | "closed" | "reopened" | "edited" | "deleted")[],
];
/**
 * Runs your workflow anytime the project_card event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/projects/cards.
 */
export type EventObject12 = {
  types?: Types12;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types12 = [
  "created" | "moved" | "converted" | "edited" | "deleted",
  ...("created" | "moved" | "converted" | "edited" | "deleted")[],
];
/**
 * Runs your workflow anytime the project_column event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/projects/columns.
 */
export type EventObject13 = {
  types?: Types13;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types13 = [
  "created" | "updated" | "moved" | "deleted",
  ...("created" | "updated" | "moved" | "deleted")[],
];
/**
 * Runs your workflow anytime the pull_request event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/pulls.
 * Note: Workflows do not run on private base repositories when you open a pull request from a forked repository.
 * When you create a pull request from a forked repository to the base repository, GitHub sends the pull_request event to the base repository and no pull request events occur on the forked repository.
 * Workflows don't run on forked repositories by default. You must enable GitHub Actions in the Actions tab of the forked repository.
 * The permissions for the GITHUB_TOKEN in forked repositories is read-only. For more information about the GITHUB_TOKEN, see https://help.github.com/en/articles/virtual-environments-for-github-actions.
 */
export type Ref = {
  types?: Types14;
  /**
   * This interface was referenced by `undefined`'s JSON-Schema definition
   * via the `patternProperty` "^(branche|tag|path)s(-ignore)?$".
   */
  [k: string]: unknown[] | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types14 = [
  (
    | "assigned"
    | "unassigned"
    | "labeled"
    | "unlabeled"
    | "opened"
    | "edited"
    | "closed"
    | "reopened"
    | "synchronize"
    | "converted_to_draft"
    | "ready_for_review"
    | "locked"
    | "unlocked"
    | "review_requested"
    | "review_request_removed"
    | "auto_merge_enabled"
    | "auto_merge_disabled"
  ),
  ...(
    | "assigned"
    | "unassigned"
    | "labeled"
    | "unlabeled"
    | "opened"
    | "edited"
    | "closed"
    | "reopened"
    | "synchronize"
    | "converted_to_draft"
    | "ready_for_review"
    | "locked"
    | "unlocked"
    | "review_requested"
    | "review_request_removed"
    | "auto_merge_enabled"
    | "auto_merge_disabled"
  )[],
];
/**
 * Runs your workflow anytime the pull_request_review event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/pulls/reviews.
 * Note: Workflows do not run on private base repositories when you open a pull request from a forked repository.
 * When you create a pull request from a forked repository to the base repository, GitHub sends the pull_request event to the base repository and no pull request events occur on the forked repository.
 * Workflows don't run on forked repositories by default. You must enable GitHub Actions in the Actions tab of the forked repository.
 * The permissions for the GITHUB_TOKEN in forked repositories is read-only. For more information about the GITHUB_TOKEN, see https://help.github.com/en/articles/virtual-environments-for-github-actions.
 */
export type EventObject14 = {
  types?: Types15;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types15 = [
  "submitted" | "edited" | "dismissed",
  ...("submitted" | "edited" | "dismissed")[],
];
/**
 * Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the pull_request_review_comment event. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/pulls/comments.
 * Note: Workflows do not run on private base repositories when you open a pull request from a forked repository.
 * When you create a pull request from a forked repository to the base repository, GitHub sends the pull_request event to the base repository and no pull request events occur on the forked repository.
 * Workflows don't run on forked repositories by default. You must enable GitHub Actions in the Actions tab of the forked repository.
 * The permissions for the GITHUB_TOKEN in forked repositories is read-only. For more information about the GITHUB_TOKEN, see https://help.github.com/en/articles/virtual-environments-for-github-actions.
 */
export type EventObject15 = {
  types?: Types16;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types16 = [
  "created" | "edited" | "deleted",
  ...("created" | "edited" | "deleted")[],
];
/**
 * This event is similar to pull_request, except that it runs in the context of the base repository of the pull request, rather than in the merge commit. This means that you can more safely make your secrets available to the workflows triggered by the pull request, because only workflows defined in the commit on the base repository are run. For example, this event allows you to create workflows that label and comment on pull requests, based on the contents of the event payload.
 */
export type Ref1 = {
  types?: Types17;
  /**
   * This interface was referenced by `undefined`'s JSON-Schema definition
   * via the `patternProperty` "^(branche|tag|path)s(-ignore)?$".
   */
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types17 = [
  (
    | "assigned"
    | "unassigned"
    | "labeled"
    | "unlabeled"
    | "opened"
    | "edited"
    | "closed"
    | "reopened"
    | "synchronize"
    | "converted_to_draft"
    | "ready_for_review"
    | "locked"
    | "unlocked"
    | "review_requested"
    | "review_request_removed"
    | "auto_merge_enabled"
    | "auto_merge_disabled"
  ),
  ...(
    | "assigned"
    | "unassigned"
    | "labeled"
    | "unlabeled"
    | "opened"
    | "edited"
    | "closed"
    | "reopened"
    | "synchronize"
    | "converted_to_draft"
    | "ready_for_review"
    | "locked"
    | "unlocked"
    | "review_requested"
    | "review_request_removed"
    | "auto_merge_enabled"
    | "auto_merge_disabled"
  )[],
];
/**
 * Runs your workflow when someone pushes to a repository branch, which triggers the push event.
 * Note: The webhook payload available to GitHub Actions does not include the added, removed, and modified attributes in the commit object. You can retrieve the full commit object using the REST API. For more information, see https://developer.github.com/v3/repos/commits/#get-a-single-commit.
 */
export type Ref2 = {
  branches?: Branch;
  "branches-ignore"?: Branch;
  tags?: Branch;
  "tags-ignore"?: Branch;
  paths?: Path;
  "paths-ignore"?: Path;
  /**
   * This interface was referenced by `undefined`'s JSON-Schema definition
   * via the `patternProperty` "^(branche|tag|path)s(-ignore)?$".
   */
  [k: string]: string[] | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * When using the push and pull_request events, you can configure a workflow to run on specific branches or tags. If you only define only tags or only branches, the workflow won't run for events affecting the undefined Git ref.
 * The branches, branches-ignore, tags, and tags-ignore keywords accept glob patterns that use the * and ** wildcard characters to match more than one branch or tag name. For more information, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet.
 * The patterns defined in branches and tags are evaluated against the Git ref's name. For example, defining the pattern mona/octocat in branches will match the refs/heads/mona/octocat Git ref. The pattern releases/** will match the refs/heads/releases/10 Git ref.
 * You can use two types of filters to prevent a workflow from running on pushes and pull requests to tags and branches:
 * - branches or branches-ignore - You cannot use both the branches and branches-ignore filters for the same event in a workflow. Use the branches filter when you need to filter branches for positive matches and exclude branches. Use the branches-ignore filter when you only need to exclude branch names.
 * - tags or tags-ignore - You cannot use both the tags and tags-ignore filters for the same event in a workflow. Use the tags filter when you need to filter tags for positive matches and exclude tags. Use the tags-ignore filter when you only need to exclude tag names.
 * You can exclude tags and branches using the ! character. The order that you define patterns matters.
 * - A matching negative pattern (prefixed with !) after a positive match will exclude the Git ref.
 * - A matching positive pattern after a negative match will include the Git ref again.
 *
 * @minItems 1
 */
export type Branch = [string, ...string[]];
/**
 * When using the push and pull_request events, you can configure a workflow to run when at least one file does not match paths-ignore or at least one modified file matches the configured paths. Path filters are not evaluated for pushes to tags.
 * The paths-ignore and paths keywords accept glob patterns that use the * and ** wildcard characters to match more than one path name. For more information, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet.
 * You can exclude paths using two types of filters. You cannot use both of these filters for the same event in a workflow.
 * - paths-ignore - Use the paths-ignore filter when you only need to exclude path names.
 * - paths - Use the paths filter when you need to filter paths for positive matches and exclude paths.
 *
 * @minItems 1
 */
export type Path = [string, ...string[]];
/**
 * Runs your workflow anytime a package is published or updated. For more information, see https://help.github.com/en/github/managing-packages-with-github-packages.
 */
export type EventObject16 = {
  types?: Types18;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types18 = ["published" | "updated", ...("published" | "updated")[]];
/**
 * Runs your workflow anytime the release event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/repos/releases/ in the GitHub Developer documentation.
 */
export type EventObject17 = {
  types?: Types19;
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types19 = [
  (
    | "published"
    | "unpublished"
    | "created"
    | "edited"
    | "deleted"
    | "prereleased"
    | "released"
  ),
  ...(
    | "published"
    | "unpublished"
    | "created"
    | "edited"
    | "deleted"
    | "prereleased"
    | "released"
  )[],
];
/**
 * This event occurs when a workflow run is requested or completed, and allows you to execute a workflow based on the finished result of another workflow. For example, if your pull_request workflow generates build artifacts, you can create a new workflow that uses workflow_run to analyze the results and add a comment to the original pull request.
 */
export type EventObject18 = {
  types?: Types20;
  /**
   * @minItems 1
   */
  workflows?: [string, ...string[]];
  [k: string]: unknown | undefined;
} & ({
  [k: string]: unknown | undefined;
} | null);
/**
 * Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.
 * You can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.
 *
 * @minItems 1
 */
export type Types20 = [
  "requested" | "completed",
  ...("requested" | "completed")[],
];
export type StringContainingExpressionSyntax = string;
/**
 * You can override the default shell settings in the runner's operating system using the shell keyword. You can use built-in shell keywords, or you can define a custom set of shell options.
 */
export type Shell =
  | string
  | ("bash" | "pwsh" | "python" | "sh" | "cmd" | "powershell");
/**
 * Using the working-directory keyword, you can specify the working directory of where to run the command.
 */
export type WorkingDirectory = string;
export type ExpressionSyntax = string;
/**
 * Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional statement that causes the job to continue.
 */
export type JobNeeds = [Name, ...Name[]] | Name;
export type Name = string;
/**
 * You can modify the default permissions granted to the GITHUB_TOKEN, adding or removing access as required, so that you only allow the minimum required access.
 */
export type Permissions = ("read-all" | "write-all") | PermissionsEvent;
export type PermissionsLevel = "read" | "write" | "none";
/**
 * To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the jobs.<job_id>.steps[*].env, jobs.<job_id>.env, and env keywords. For more information, see https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv
 */
export type Env = {
  args?: string;
  entrypoint?: string;
  [k: string]: unknown | undefined;
} & (
  | {
      [k: string]: (string | number | boolean) | undefined;
    }
  | StringContainingExpressionSyntax
);
/**
 * A build matrix is a set of different configurations of the virtual environment. For example you might run a job against more than one supported version of a language, operating system, or tool. Each configuration is a copy of the job that runs and reports a status.
 * You can specify a matrix by supplying an array for the configuration options. For example, if the GitHub virtual environment supports Node.js versions 6, 8, and 10 you could specify an array of those versions in the matrix.
 * When you define a matrix of operating systems, you must set the required runs-on keyword to the operating system of the current job, rather than hard-coding the operating system name. To access the operating system name, you can use the matrix.os context parameter to set runs-on. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.
 */
export type Matrix =
  | {
      [k: string]: unknown | undefined;
    }
  | ExpressionSyntax;
/**
 * To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the jobs.<job_id>.steps[*].env, jobs.<job_id>.env, and env keywords. For more information, see https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv
 */
export type Env1 =
  | {
      [k: string]: (string | number | boolean) | undefined;
    }
  | StringContainingExpressionSyntax;

export interface GitHubActionsWorkflowConfig {
  /**
   * The name of your workflow. GitHub displays the names of your workflows on your repository's actions page. If you omit this field, GitHub sets the name to the workflow's filename.
   */
  name?: string;
  /**
   * The name of the GitHub event that triggers the workflow. You can provide a single event string, array of events, array of event types, or an event configuration map that schedules a workflow or restricts the execution of a workflow to specific files, tags, or branch changes. For a list of available events, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows.
   */
  on:
    | Event
    | [Event, ...Event[]]
    | {
        branch_protection_rule?: EventObject;
        check_run?: EventObject1;
        check_suite?: EventObject2;
        /**
         * Runs your workflow anytime someone creates a branch or tag, which triggers the create event. For information about the REST API, see https://developer.github.com/v3/git/refs/#create-a-reference.
         */
        create?: {
          [k: string]: unknown | undefined;
        } | null;
        /**
         * Runs your workflow anytime someone deletes a branch or tag, which triggers the delete event. For information about the REST API, see https://developer.github.com/v3/git/refs/#delete-a-reference.
         */
        delete?: {
          [k: string]: unknown | undefined;
        } | null;
        /**
         * Runs your workflow anytime someone creates a deployment, which triggers the deployment event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see https://developer.github.com/v3/repos/deployments/.
         */
        deployment?: {
          [k: string]: unknown | undefined;
        } | null;
        /**
         * Runs your workflow anytime a third party provides a deployment status, which triggers the deployment_status event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see https://developer.github.com/v3/repos/deployments/#create-a-deployment-status.
         */
        deployment_status?: {
          [k: string]: unknown | undefined;
        } | null;
        discussion?: EventObject3;
        discussion_comment?: EventObject4;
        /**
         * Runs your workflow anytime when someone forks a repository, which triggers the fork event. For information about the REST API, see https://developer.github.com/v3/repos/forks/#create-a-fork.
         */
        fork?: {
          [k: string]: unknown | undefined;
        } | null;
        /**
         * Runs your workflow when someone creates or updates a Wiki page, which triggers the gollum event.
         */
        gollum?: {
          [k: string]: unknown | undefined;
        } | null;
        issue_comment?: EventObject5;
        issues?: EventObject6;
        label?: EventObject7;
        member?: EventObject8;
        merge_group?: EventObject9;
        milestone?: EventObject10;
        /**
         * Runs your workflow anytime someone pushes to a GitHub Pages-enabled branch, which triggers the page_build event. For information about the REST API, see https://developer.github.com/v3/repos/pages/.
         */
        page_build?: {
          [k: string]: unknown | undefined;
        } | null;
        project?: EventObject11;
        project_card?: EventObject12;
        project_column?: EventObject13;
        /**
         * Runs your workflow anytime someone makes a private repository public, which triggers the public event. For information about the REST API, see https://developer.github.com/v3/repos/#edit.
         */
        public?: {
          [k: string]: unknown | undefined;
        } | null;
        pull_request?: Ref;
        pull_request_review?: EventObject14;
        pull_request_review_comment?: EventObject15;
        pull_request_target?: Ref1;
        push?: Ref2;
        registry_package?: EventObject16;
        release?: EventObject17;
        /**
         * Runs your workflow anytime the status of a Git commit changes, which triggers the status event. For information about the REST API, see https://developer.github.com/v3/repos/statuses/.
         */
        status?: {
          [k: string]: unknown | undefined;
        } | null;
        /**
         * Runs your workflow anytime the watch event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/activity/starring/.
         */
        watch?: {
          [k: string]: unknown | undefined;
        } | null;
        /**
         * Allows workflows to be reused by other workflows.
         */
        workflow_call?: {
          /**
           * When using the workflow_call keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow.
           */
          inputs?: {
            /**
             * A string identifier to associate with the input. The value of <input_id> is a map of the input's metadata. The <input_id> must be a unique identifier within the inputs object. The <input_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.
             *
             * This interface was referenced by `undefined`'s JSON-Schema definition
             * via the `patternProperty` "^[_a-zA-Z][a-zA-Z0-9_-]*$".
             */
            [k: string]:
              | {
                  /**
                   * A string description of the input parameter.
                   */
                  description?: string;
                  /**
                   * A string shown to users using the deprecated input.
                   */
                  deprecationMessage?: string;
                  /**
                   * A boolean to indicate whether the action requires the input parameter. Set to true when the parameter is required.
                   */
                  required?: boolean;
                  /**
                   * Required if input is defined for the on.workflow_call keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: boolean, number, or string.
                   */
                  type: "boolean" | "number" | "string";
                  /**
                   * The default value is used when an input parameter isn't specified in a workflow file.
                   */
                  default?: boolean | number | string;
                }
              | undefined;
          };
          /**
           * A map of the secrets that can be used in the called workflow. Within the called workflow, you can use the secrets context to refer to a secret.
           */
          secrets?: {
            /**
             * A string identifier to associate with the secret.
             *
             * This interface was referenced by `undefined`'s JSON-Schema definition
             * via the `patternProperty` "^[_a-zA-Z][a-zA-Z0-9_-]*$".
             */
            [k: string]:
              | {
                  /**
                   * A string description of the secret parameter.
                   */
                  description?: string;
                  /**
                   * A boolean specifying whether the secret must be supplied.
                   */
                  required: boolean;
                }
              | undefined;
          };
          [k: string]: unknown | undefined;
        };
        /**
         * You can now create workflows that are manually triggered with the new workflow_dispatch event. You will then see a 'Run workflow' button on the Actions tab, enabling you to easily trigger a run.
         */
        workflow_dispatch?: {
          /**
           * Input parameters allow you to specify data that the action expects to use during runtime. GitHub stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.
           */
          inputs?: {
            /**
             * A string identifier to associate with the input. The value of <input_id> is a map of the input's metadata. The <input_id> must be a unique identifier within the inputs object. The <input_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.
             *
             * This interface was referenced by `undefined`'s JSON-Schema definition
             * via the `patternProperty` "^[_a-zA-Z][a-zA-Z0-9_-]*$".
             */
            [k: string]:
              | {
                  [k: string]: unknown | undefined;
                }
              | undefined;
          };
          [k: string]: unknown | undefined;
        };
        workflow_run?: EventObject18;
        /**
         * You can use the GitHub API to trigger a webhook event called repository_dispatch when you want to trigger a workflow for activity that happens outside of GitHub. For more information, see https://developer.github.com/v3/repos/#create-a-repository-dispatch-event.
         * To trigger the custom repository_dispatch webhook event, you must send a POST request to a GitHub API endpoint and provide an event_type name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the repository_dispatch event.
         */
        repository_dispatch?: {
          [k: string]: unknown | undefined;
        } | null;
        /**
         * You can schedule a workflow to run at specific UTC times using POSIX cron syntax (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Scheduled workflows run on the latest commit on the default or base branch. The shortest interval you can run scheduled workflows is once every 5 minutes.
         * Note: GitHub Actions does not support the non-standard syntax @yearly, @monthly, @weekly, @daily, @hourly, and @reboot.
         * You can use crontab guru (https://crontab.guru/). to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of crontab guru examples (https://crontab.guru/examples.html).
         *
         * @minItems 1
         */
        schedule?: [
          {
            cron?: string;
          },
          ...{
            cron?: string;
          }[],
        ];
      };
  /**
   * To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the jobs.<job_id>.steps[*].env, jobs.<job_id>.env, and env keywords. For more information, see https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv
   */
  env?:
    | {
        [k: string]: (string | number | boolean) | undefined;
      }
    | StringContainingExpressionSyntax;
  defaults?: Defaults;
  /**
   * Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the secrets context.
   * You can also specify concurrency at the workflow level.
   * When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.
   */
  concurrency?: string | Concurrency;
  /**
   * A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the jobs.<job_id>.needs keyword.
   * Each job runs in a fresh instance of the virtual environment specified by runs-on.
   * You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#usage-limits.
   */
  jobs: {
    /**
     * This interface was referenced by `undefined`'s JSON-Schema definition
     * via the `patternProperty` "^[_a-zA-Z][a-zA-Z0-9_-]*$".
     */
    [k: string]: (NormalJob | ReusableWorkflowCallJob) | undefined;
  };
  /**
   * The name for workflow runs generated from the workflow. GitHub displays the workflow run name in the list of workflow runs on your repository's 'Actions' tab.
   */
  "run-name"?: string;
  permissions?: Permissions;
}
/**
 * A map of default settings that will apply to all jobs in the workflow.
 */
export interface Defaults {
  run?: {
    shell?: Shell;
    "working-directory"?: WorkingDirectory;
  };
}
export interface Concurrency {
  /**
   * When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled.
   */
  group: string;
  /**
   * To cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.
   */
  "cancel-in-progress"?: boolean | ExpressionSyntax;
}
/**
 * Each job must have an id to associate with the job. The key job_id is a string and its value is a map of the job's configuration data. You must replace <job_id> with a string that is unique to the jobs object. The <job_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.
 */
export interface NormalJob {
  /**
   * The name of the job displayed on GitHub.
   */
  name?: string;
  needs?: JobNeeds;
  permissions?: Permissions;
  /**
   * The type of machine to run the job on. The machine can be either a GitHub-hosted runner, or a self-hosted runner.
   */
  "runs-on":
    | string
    | ([string] & unknown[])
    | {
        group?: string;
        labels?: string | string[];
        [k: string]: unknown | undefined;
      }
    | StringContainingExpressionSyntax
    | ExpressionSyntax;
  /**
   * The environment that the job references.
   */
  environment?: string | Environment;
  /**
   * A map of outputs for a job. Job outputs are available to all downstream jobs that depend on this job.
   */
  outputs?: {
    [k: string]: string | undefined;
  };
  /**
   * To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the jobs.<job_id>.steps[*].env, jobs.<job_id>.env, and env keywords. For more information, see https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv
   */
  env?:
    | {
        [k: string]: (string | number | boolean) | undefined;
      }
    | StringContainingExpressionSyntax;
  defaults?: Defaults1;
  /**
   * You can use the if conditional to prevent a job from running unless a condition is met. You can use any supported context and expression to create a conditional.
   * Expressions in an if conditional do not require the ${{ }} syntax. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.
   */
  if?: boolean | number | string;
  /**
   * A job contains a sequence of tasks called steps. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the virtual environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. GitHub provides built-in steps to set up and complete a job.
   * Must contain either `uses` or `run`
   *
   *
   * @minItems 1
   */
  steps?: [
    (
      | {
          uses: string;
          [k: string]: unknown | undefined;
        }
      | {
          run: string;
          [k: string]: unknown | undefined;
        }
    ) & {
      /**
       * A unique identifier for the step. You can use the id to reference the step in contexts. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.
       */
      id?: string;
      /**
       * You can use the if conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
       * Expressions in an if conditional do not require the ${{ }} syntax. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.
       */
      if?: boolean | number | string;
      /**
       * A name for your step to display on GitHub.
       */
      name?: string;
      /**
       * Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a published Docker container image (https://hub.docker.com/).
       * We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.
       * - Using the commit SHA of a released action version is the safest for stability and security.
       * - Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work.
       * - Using the master branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.
       * Some actions require inputs that you must set using the with keyword. Review the action's README file to determine the inputs required.
       * Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux virtual environment. For more details, see https://help.github.com/en/articles/virtual-environments-for-github-actions.
       */
      uses?: string;
      /**
       * Runs command-line programs using the operating system's shell. If you do not provide a name, the step name will default to the text specified in the run command.
       * Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#using-a-specific-shell.
       * Each run keyword represents a new process and shell in the virtual environment. When you provide multi-line commands, each line runs in the same shell.
       */
      run?: string;
      "working-directory"?: WorkingDirectory;
      shell?: Shell;
      with?: Env;
      /**
       * To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the jobs.<job_id>.steps[*].env, jobs.<job_id>.env, and env keywords. For more information, see https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv
       */
      env?:
        | {
            [k: string]: (string | number | boolean) | undefined;
          }
        | StringContainingExpressionSyntax;
      /**
       * Prevents a job from failing when a step fails. Set to true to allow a job to pass when this step fails.
       */
      "continue-on-error"?: boolean | ExpressionSyntax;
      /**
       * The maximum number of minutes to run the step before killing the process.
       */
      "timeout-minutes"?: number | ExpressionSyntax;
    },
    ...((
      | {
          uses: string;
          [k: string]: unknown | undefined;
        }
      | {
          run: string;
          [k: string]: unknown | undefined;
        }
    ) & {
      /**
       * A unique identifier for the step. You can use the id to reference the step in contexts. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.
       */
      id?: string;
      /**
       * You can use the if conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
       * Expressions in an if conditional do not require the ${{ }} syntax. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.
       */
      if?: boolean | number | string;
      /**
       * A name for your step to display on GitHub.
       */
      name?: string;
      /**
       * Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a published Docker container image (https://hub.docker.com/).
       * We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.
       * - Using the commit SHA of a released action version is the safest for stability and security.
       * - Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work.
       * - Using the master branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.
       * Some actions require inputs that you must set using the with keyword. Review the action's README file to determine the inputs required.
       * Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux virtual environment. For more details, see https://help.github.com/en/articles/virtual-environments-for-github-actions.
       */
      uses?: string;
      /**
       * Runs command-line programs using the operating system's shell. If you do not provide a name, the step name will default to the text specified in the run command.
       * Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#using-a-specific-shell.
       * Each run keyword represents a new process and shell in the virtual environment. When you provide multi-line commands, each line runs in the same shell.
       */
      run?: string;
      "working-directory"?: WorkingDirectory;
      shell?: Shell;
      with?: Env;
      /**
       * To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the jobs.<job_id>.steps[*].env, jobs.<job_id>.env, and env keywords. For more information, see https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv
       */
      env?:
        | {
            [k: string]: (string | number | boolean) | undefined;
          }
        | StringContainingExpressionSyntax;
      /**
       * Prevents a job from failing when a step fails. Set to true to allow a job to pass when this step fails.
       */
      "continue-on-error"?: boolean | ExpressionSyntax;
      /**
       * The maximum number of minutes to run the step before killing the process.
       */
      "timeout-minutes"?: number | ExpressionSyntax;
    })[],
  ];
  /**
   * The maximum number of minutes to let a workflow run before GitHub automatically cancels it. Default: 360
   */
  "timeout-minutes"?: number | ExpressionSyntax;
  /**
   * A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in.
   */
  strategy?: {
    matrix: Matrix;
    /**
     * When set to true, GitHub cancels all in-progress jobs if any matrix job fails. Default: true
     */
    "fail-fast"?: boolean | string;
    /**
     * The maximum number of jobs that can run simultaneously when using a matrix job strategy. By default, GitHub will maximize the number of jobs run in parallel depending on the available runners on GitHub-hosted virtual machines.
     */
    "max-parallel"?: number | string;
  };
  /**
   * Prevents a workflow run from failing when a job fails. Set to true to allow a workflow run to pass when this job fails.
   */
  "continue-on-error"?: boolean | ExpressionSyntax;
  /**
   * A container to run any steps in a job that don't already specify a container. If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts.
   * If you do not set a container, all steps will run directly on the host specified by runs-on unless a step refers to an action configured to run in a container.
   */
  container?: string | Container;
  /**
   * Additional containers to host services for a job in a workflow. These are useful for creating databases or cache services like redis. The runner on the virtual machine will automatically create a network and manage the life cycle of the service containers.
   * When you use a service container for a job or your step uses container actions, you don't need to set port information to access the service. Docker automatically exposes all ports between containers on the same network.
   * When both the job and the action run in a container, you can directly reference the container by its hostname. The hostname is automatically mapped to the service name.
   * When a step does not use a container action, you must access the service using localhost and bind the ports.
   */
  services?: {
    [k: string]: Container;
  };
  /**
   * Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the secrets context.
   * You can also specify concurrency at the workflow level.
   * When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.
   */
  concurrency?: string | Concurrency;
}
export interface PermissionsEvent {
  actions?: PermissionsLevel;
  checks?: PermissionsLevel;
  contents?: PermissionsLevel;
  deployments?: PermissionsLevel;
  discussions?: PermissionsLevel;
  "id-token"?: PermissionsLevel;
  issues?: PermissionsLevel;
  packages?: PermissionsLevel;
  pages?: PermissionsLevel;
  "pull-requests"?: PermissionsLevel;
  "repository-projects"?: PermissionsLevel;
  "security-events"?: PermissionsLevel;
  statuses?: PermissionsLevel;
}
/**
 * The environment that the job references
 */
export interface Environment {
  /**
   * The name of the environment configured in the repo.
   */
  name: string;
  /**
   * A deployment URL
   */
  url?: string;
}
/**
 * A map of default settings that will apply to all steps in the job.
 */
export interface Defaults1 {
  run?: {
    shell?: Shell;
    "working-directory"?: WorkingDirectory;
  };
}
export interface Container {
  /**
   * The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a registry name.
   */
  image: string;
  /**
   * If the image's container registry requires authentication to pull the image, you can use credentials to set a map of the username and password. The credentials are the same values that you would provide to the `docker login` command.
   */
  credentials?: {
    username?: string;
    password?: string;
    [k: string]: unknown | undefined;
  };
  /**
   * Sets an array of environment variables in the container.
   */
  env?:
    | {
        [k: string]: (string | number | boolean) | undefined;
      }
    | StringContainingExpressionSyntax;
  /**
   * Sets an array of ports to expose on the container.
   *
   * @minItems 1
   */
  ports?: [number | string, ...(number | string)[]];
  /**
   * Sets an array of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host.
   * To specify a volume, you specify the source and destination path: <source>:<destinationPath>
   * The <source> is a volume name or an absolute path on the host machine, and <destinationPath> is an absolute path in the container.
   *
   * @minItems 1
   */
  volumes?: [string, ...string[]];
  /**
   * Additional Docker container resource options. For a list of options, see https://docs.docker.com/engine/reference/commandline/create/#options.
   */
  options?: string;
}
/**
 * Each job must have an id to associate with the job. The key job_id is a string and its value is a map of the job's configuration data. You must replace <job_id> with a string that is unique to the jobs object. The <job_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.
 */
export interface ReusableWorkflowCallJob {
  /**
   * The name of the job displayed on GitHub.
   */
  name?: string;
  needs?: JobNeeds;
  permissions?: Permissions;
  /**
   * You can use the if conditional to prevent a job from running unless a condition is met. You can use any supported context and expression to create a conditional.
   * Expressions in an if conditional do not require the ${{ }} syntax. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.
   */
  if?: boolean | number | string;
  /**
   * The location and version of a reusable workflow file to run as a job, of the form './{path/to}/{localfile}.yml' or '{owner}/{repo}/{path}/{filename}@{ref}'. {ref} can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security.
   */
  uses: string;
  /**
   * A map of inputs that are passed to the called workflow. Any inputs that you pass must match the input specifications defined in the called workflow. Unlike 'jobs.<job_id>.steps[*].with', the inputs you pass with 'jobs.<job_id>.with' are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the inputs context.
   */
  with?:
    | {
        [k: string]: (string | number | boolean) | undefined;
      }
    | StringContainingExpressionSyntax;
  /**
   * When a job is used to call a reusable workflow, you can use 'secrets' to provide a map of secrets that are passed to the called workflow. Any secrets that you pass must match the names defined in the called workflow.
   */
  secrets?: Env1 | "inherit";
  /**
   * A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in.
   */
  strategy?: {
    matrix: Matrix;
    /**
     * When set to true, GitHub cancels all in-progress jobs if any matrix job fails. Default: true
     */
    "fail-fast"?: boolean | string;
    /**
     * The maximum number of jobs that can run simultaneously when using a matrix job strategy. By default, GitHub will maximize the number of jobs run in parallel depending on the available runners on GitHub-hosted virtual machines.
     */
    "max-parallel"?: number | string;
  };
  /**
   * Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the secrets context.
   * You can also specify concurrency at the workflow level.
   * When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.
   */
  concurrency?: string | Concurrency;
}