Add configuration files for CI/CD and examples by highgroundbkk · Pull Request #1438 · github/awesome-copilot

highgroundbkk · 2026-04-18T10:10:23Z

Pull Request Checklist

I have read and followed the CONTRIBUTING.md guidelines.
I have read and followed the Guidance for submissions involving paid services.
My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
The file follows the required naming convention.
The content is clearly structured and follows the example format.
I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
I have run npm start and verified that README.md is up to date.
I am targeting the staged branch for this pull request.

Description

Type of Contribution

Additional Notes

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Create deno.yml

Co-authored-by: highgroundbkk <245770312+highgroundbkk@users.noreply.github.com>

Add gh-runtime-cli extension example to gh-cli skill

github-actions

⚠️ This PR targets main, but PRs should target staged.

The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.

You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 1438 --base staged

Copilot

Pull request overview

Adds several GitHub Actions workflow files intended for CI/CD examples/templates and updates the GH CLI skill documentation with an additional extension install example.

Changes:

Added multiple GitHub Actions workflows (Webpack, Terraform, Labeler, Google GKE deploy, Deno, CodeQL).
Updated the gh-cli skill to include installation instructions for an additional GitHub CLI extension.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 13 comments.

Show a summary per file

File	Description
skills/gh-cli/SKILL.md	Adds an example command to install a GitHub CLI extension.
.github/workflows/webpack.yml	Introduces a Node/Webpack workflow (currently malformed and not aligned with repo tooling).
.github/workflows/terraform.yml	Introduces a Terraform workflow (currently malformed and not applicable to repo contents).
.github/workflows/label.yml	Introduces a PR labeler workflow (currently malformed and missing required repo config).
.github/workflows/google.yml	Introduces a GKE deploy workflow (contains trigger/config issues and a broken kustomize install step).
.github/workflows/deno.yml	Introduces a Deno lint/test workflow (likely incompatible with this repo’s Node-based scripts).
.github/workflows/codeql.yml	Introduces a CodeQL workflow (currently malformed YAML).

Copilot · 2026-04-18T10:16:40Z

+    - name: Terraform Apply
+      if: github.ref == 'refs/heads/"main"' && github.event_name == 'push'
+      run: terraform apply -auto-approve -input=false


The apply guard will never match because github.ref for main is refs/heads/main, but the condition checks refs/heads/"main" (extra quotes). Update the ref comparison (and consider using github.ref_name == 'main' for clarity).

Copilot · 2026-04-18T10:16:40Z

+    # Initialize a new or existing Terraform working directory by creating initial files, loading any remote state, downloading modules, etc.
+    - name: Terraform Init
+      run: terraform init
+
+    # Checks that all Terraform configuration files adhere to a canonical format
+    - name: Terraform Format
+      run: terraform fmt -check
+
+    # Generates an execution plan for Terraform
+    - name: Terraform Plan
+      run: terraform plan -input=false


This workflow runs terraform init/fmt/plan but the repository does not contain any .tf files, so the job will fail when it executes on main. If this is meant to be a reusable example, it should not be enabled in this repo’s CI (e.g. move it to documentation/examples or change on: to workflow_dispatch).

Copilot · 2026-04-18T10:16:40Z

+      # Set up kustomize
+      - name: 'Set up Kustomize'
+        run: |-
+          curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.4.3/kustomize_v5.4.3_linux_amd64.tar.gz


The Kustomize install step downloads a .tar.gz archive but saves it as kustomize and then marks it executable without extracting it. This will fail when ./kustomize is executed. Download the correct binary or extract the archive before chmod/using it.

Suggested change

curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.4.3/kustomize_v5.4.3_linux_amd64.tar.gz

curl -sfLo kustomize.tar.gz https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.4.3/kustomize_v5.4.3_linux_amd64.tar.gz

tar -xzf kustomize.tar.gz

Copilot · 2026-04-18T10:16:41Z

+# To use this workflow, you will need to set up a .github/labeler.yml
+# file with configuration.  For more information, see:
+# https://github.com/actions/labeler
+
+name: Labeler
+on: [pull_request_target]
+
+jobs:
+  label:
+
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+
+    steps:
+    - uses: actions/labeler@v4
+      with:
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"


This workflow requires a .github/labeler.yml configuration file (as noted in the header comment), but the repository does not contain one. As a result, the action will fail when it runs. Either add the corresponding .github/labeler.yml config or remove/disable this workflow (e.g., make it workflow_dispatch) until it’s configured.

Copilot · 2026-04-18T10:16:41Z

+        - language: actions
+          build-mode: none
+        - language: javascript-typescript
+          build-mode: none


The matrix include list is mis-indented: the - language: entries need to be nested under include:. As written, this YAML is invalid and the workflow won’t load.

Suggested change

- language: actions

build-mode: none

- language: javascript-typescript

build-mode: none

- language: actions

build-mode: none

- language: javascript-typescript

build-mode: none

Copilot · 2026-04-18T10:16:42Z

+on:
+  push:
+    branches:
+      - '"main"'


The branch filter is set to "main" (including quotes), so this workflow will never trigger on pushes to main. Use main (or 'main') as the branch name.

Suggested change

- '"main"'

- 'main'

Copilot · 2026-04-18T10:16:42Z

+env:
+  PROJECT_ID: 'my-project' # TODO: update to your Google Cloud project ID
+  GAR_LOCATION: 'us-central1' # TODO: update to your region
+  GKE_CLUSTER: 'cluster-1' # TODO: update to your cluster name
+  GKE_ZONE: 'us-central1-c' # TODO: update to your cluster zone
+  DEPLOYMENT_NAME: 'gke-test' # TODO: update to your deployment name
+  REPOSITORY: 'samples' # TODO: update to your Artifact Registry docker repository name
+  IMAGE: 'static-site'
+  WORKLOAD_IDENTITY_PROVIDER: 'projects/123456789/locations/global/workloadIdentityPools/my-pool/providers/my-provider' # TODO: update to your workload identity provider


This workflow is written as a template (multiple TODO placeholders and assumes GKE manifests/kubectl access). Since it is enabled on push to main, it will run in this repository and fail unless fully configured. If the intent is to provide an example, consider moving it out of .github/workflows/ or changing on: to workflow_dispatch so it doesn’t execute by default.

Copilot · 2026-04-18T10:16:42Z

+    - uses: actions/labeler@v4
+      with:
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"


steps: is defined, but the - uses: entry is not indented under it, making the workflow YAML invalid. Indent the step list item(s) under steps: so GitHub Actions can parse the workflow.

Suggested change

- uses: actions/labeler@v4

with:

repo-token: "${{ secrets.GITHUB_TOKEN }}"

- uses: actions/labeler@v4

with:

repo-token: "${{ secrets.GITHUB_TOKEN }}"

Copilot · 2026-04-18T10:16:43Z

+        run: deno lint
+
+      - name: Run tests
+        run: deno test -A


This workflow runs deno lint from the repository root, but the repo contains Node.js scripts under eng/ that use Node globals like process (e.g. eng/update-readme.mjs), which deno lint will flag as undefined. If the intent is to lint a Deno project, scope the lint/test commands to a Deno-specific subdirectory (or add a deno.json with appropriate lint.files.include/exclude).

Suggested change

run: deno lint

- name: Run tests

run: deno test -A

run: deno lint --ignore=eng

- name: Run tests

run: deno test -A --ignore=eng

Copilot · 2026-04-18T10:16:43Z

+    # Checkout the repository to the GitHub Actions runner
+    - name: Checkout
+      uses: actions/checkout@v4
+
+    # Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token
+    - name: Setup Terraform
+      uses: hashicorp/setup-terraform@v1
+      with:
+        cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}
+
+    # Initialize a new or existing Terraform working directory by creating initial files, loading any remote state, downloading modules, etc.
+    - name: Terraform Init
+      run: terraform init
+
+    # Checks that all Terraform configuration files adhere to a canonical format
+    - name: Terraform Format
+      run: terraform fmt -check
+
+    # Generates an execution plan for Terraform
+    - name: Terraform Plan
+      run: terraform plan -input=false
+
+      # On push to "main", build or change infrastructure according to Terraform configuration files
+      # Note: It is recommended to set up a required "strict" status check in your repository for "Terraform Cloud". See the documentation on "strict" required status checks for more information: https://help.github.com/en/github/administering-a-repository/types-of-required-status-checks
+    - name: Terraform Apply
+      if: github.ref == 'refs/heads/"main"' && github.event_name == 'push'
+      run: terraform apply -auto-approve -input=false


steps: is present but the subsequent step entries are not indented under it, which makes this workflow YAML invalid. Indent the - name: entries under steps: so the file parses correctly.

Suggested change

# Checkout the repository to the GitHub Actions runner

- name: Checkout

uses: actions/checkout@v4

# Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token

- name: Setup Terraform

uses: hashicorp/setup-terraform@v1

with:

cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}

# Initialize a new or existing Terraform working directory by creating initial files, loading any remote state, downloading modules, etc.

- name: Terraform Init

run: terraform init

# Checks that all Terraform configuration files adhere to a canonical format

- name: Terraform Format

run: terraform fmt -check

# Generates an execution plan for Terraform

- name: Terraform Plan

run: terraform plan -input=false

# On push to "main", build or change infrastructure according to Terraform configuration files

# Note: It is recommended to set up a required "strict" status check in your repository for "Terraform Cloud". See the documentation on "strict" required status checks for more information: https://help.github.com/en/github/administering-a-repository/types-of-required-status-checks

- name: Terraform Apply

if: github.ref == 'refs/heads/"main"' && github.event_name == 'push'

run: terraform apply -auto-approve -input=false

# Checkout the repository to the GitHub Actions runner

- name: Checkout

uses: actions/checkout@v4

# Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token

- name: Setup Terraform

uses: hashicorp/setup-terraform@v1

with:

cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}

# Initialize a new or existing Terraform working directory by creating initial files, loading any remote state, downloading modules, etc.

- name: Terraform Init

run: terraform init

# Checks that all Terraform configuration files adhere to a canonical format

- name: Terraform Format

run: terraform fmt -check

# Generates an execution plan for Terraform

- name: Terraform Plan

run: terraform plan -input=false

# On push to "main", build or change infrastructure according to Terraform configuration files

# Note: It is recommended to set up a required "strict" status check in your repository for "Terraform Cloud". See the documentation on "strict" required status checks for more information: https://help.github.com/en/github/administering-a-repository/types-of-required-status-checks

- name: Terraform Apply

if: github.ref == 'refs/heads/"main"' && github.event_name == 'push'

run: terraform apply -auto-approve -input=false

highgroundbkk and others added 13 commits January 14, 2026 00:14

Create label.yml

34d8865

Create webpack.yml

732c1b5

Create google.yml

4161e56

Create terraform.yml

26bb181

Create codeql.yml

7f49d09

Create deno.yml

1673a41

Merge branch 'github:main' into main

f747d5f

Merge pull request #1 from highgroundbkk/highgroundbkk-patch-1

9a15410

Create deno.yml

Merge branch 'github:main' into main

b64096c

Initial plan

a375ab9

Add gh-runtime-cli extension example to gh-cli skill

e17158f

Co-authored-by: highgroundbkk <245770312+highgroundbkk@users.noreply.github.com>

Merge pull request #2 from highgroundbkk/copilot/install-gh-runtime-cli

4cf5e3d

Add gh-runtime-cli extension example to gh-cli skill

Merge branch 'github:main' into main

a871e45

highgroundbkk requested a review from aaronpowell as a code owner April 18, 2026 10:10

Copilot AI review requested due to automatic review settings April 18, 2026 10:10

highgroundbkk had a problem deploying to production April 18, 2026 10:10 — with GitHub Actions Failure

github-actions bot requested changes Apr 18, 2026

View reviewed changes

Copilot started reviewing on behalf of highgroundbkk April 18, 2026 10:10 View session

Copilot AI reviewed Apr 18, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add configuration files for CI/CD and examples#1438

Add configuration files for CI/CD and examples#1438
highgroundbkk wants to merge 13 commits intogithub:mainfrom
highgroundbkk:main

highgroundbkk commented Apr 18, 2026

Uh oh!

github-actions bot left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Copilot AI Apr 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.4.3/kustomize_v5.4.3_linux_amd64.tar.gz
	curl -sfLo kustomize.tar.gz https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.4.3/kustomize_v5.4.3_linux_amd64.tar.gz
	tar -xzf kustomize.tar.gz

Conversation

highgroundbkk commented Apr 18, 2026

Pull Request Checklist

Description

Type of Contribution

Additional Notes

Uh oh!

github-actions bot left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants