From 48fee13d9ccdb895c84f1d1e0eb979149b20c7ee Mon Sep 17 00:00:00 2001
From: Will Harris <30779570+fjij@users.noreply.github.com>
Date: Wed, 29 Jan 2025 01:27:35 -0500
Subject: [PATCH] Add option to dispatch CI check manually

Fixes #15

---

For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/fjij/nix-configs/issues/15?shareId=XXXX-XXXX-XXXX-XXXX).
---
 .github/workflows/ci.yml |  1 +
 README.md                | 12 ++++++++++++
 2 files changed, 13 insertions(+)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 738e996..78400b8 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -2,6 +2,7 @@ on:
   pull_request:
   push:
     branches: [main]
+  workflow_dispatch:
 
 jobs:
   lints:
diff --git a/README.md b/README.md
index 2393e07..45e8cba 100644
--- a/README.md
+++ b/README.md
@@ -119,3 +119,15 @@ You can manually trigger the flake update CI task from the GitHub Actions interf
 3. In the left sidebar, find and click on the workflow named "Update flake.lock".
 4. Click on the "Run workflow" button.
 5. Confirm the action to manually trigger the workflow.
+
+## Manually Triggering CI Check
+
+You can manually trigger the CI check from the GitHub Actions interface. Follow these steps:
+
+1. Go to the repository on GitHub.
+2. Click on the "Actions" tab.
+3. In the left sidebar, find and click on the workflow named "CI".
+4. Click on the "Run workflow" button.
+5. Confirm the action to manually trigger the workflow.
+
+For more information on why actions don't trigger on auto-generated PRs, refer to [this discussion](https://github.com/orgs/community/discussions/55906).