chore: add daily GitHub activity automation by zakiscoding · Pull Request #121 · zakiscoding/zakiscoding

zakiscoding · 2026-03-10T18:27:15Z

Adds two scripts:

\daily-activity.ps1\ runs 5 actions daily: commit, issue, PR, review, merge across rotating repos
\setup-automation.ps1\ run once to register a Windows Scheduled Task

Run \setup-automation.ps1\ once then it fires every day at 10am automatically.

Copilot

Pull request overview

Adds a Windows Scheduled Task setup script and a daily runner script intended to automate GitHub “activity” actions (commit, issue, PR, review, merge) across a rotating set of repositories.

Changes:

Introduces setup-automation.ps1 to register/update a daily Scheduled Task at a configurable time.
Introduces daily-activity.ps1 to perform git + GitHub CLI actions against a rotating repo list.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 14 comments.

File	Description
setup-automation.ps1	Creates/updates a Scheduled Task to run the daily activity script on a schedule.
daily-activity.ps1	Implements the daily workflow (clone/pull, commit, create issue/PR, approve, merge).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-10T18:33:31Z

+$principal = New-ScheduledTaskPrincipal `
+    -UserId $env:USERNAME `
+    -LogonType S4U `
+    -RunLevel Highest


The task principal requests -RunLevel Highest. That can require admin privileges to register/run and may cause failures in non-elevated contexts; consider defaulting to LeastPrivilege (or making RunLevel configurable) unless elevation is truly required.

Copilot · 2026-03-10T18:33:31Z

+# Pick 5 repos for today, rotating evenly by day of year
+$r0 = $repos[($seed + 0) % $count]
+$r1 = $repos[($seed + 1) % $count]
+$r2 = $repos[($seed + 2) % $count]
+$r3 = $repos[($seed + 3) % $count]
+$r4 = $repos[($seed + 4) % $count]


$r3 and $r4 are computed as part of the “Pick 5 repos” rotation, but they’re never used (only r0/r1/r2 are acted on). This makes the output misleading and doesn’t match the PR description of 5 actions across rotating repos; either run Review/Merge against r3/r4 (if intended) or remove the extra repo selection/printing.

Copilot · 2026-03-10T18:33:32Z

+        try { git switch main 2>$null | Out-Null } catch {}
+        try { git pull --ff-only 2>&1 | Out-Null } catch {}
+        Pop-Location


Ensure-Cloned suppresses errors from git switch main / git pull and then returns $dir regardless. If switching/pulling fails (e.g., local changes, missing main, auth), later steps may create a PR from the wrong base or run in a stale repo state. Consider enforcing a known-good base (fetch + checkout/reset to origin/main) and failing fast when repo sync can’t be ensured.

Suggested change

try { git switch main 2>$null | Out-Null } catch {}

try { git pull --ff-only 2>&1 | Out-Null } catch {}

Pop-Location

try {

if (-not $DryRun) {

# Ensure local main matches origin/main; fail if this cannot be guaranteed

git fetch origin 2>&1 | Out-Null

git rev-parse --verify origin/main 2>&1 | Out-Null

git checkout -B main origin/main 2>&1 | Out-Null

} else {

Write-Host " DryRun: skipping git fetch/reset for $Repo"

}

} finally {

Pop-Location

}

Copilot · 2026-03-10T18:33:32Z

+    if (-not (Test-Path $dir)) {
+        Write-Host "  Cloning $Repo..."
+        if (-not $DryRun) {
+            git clone "https://github.com/$Owner/$Repo.git" $dir 2>&1 | Out-Null


When cloning, the script discards git output and doesn’t check whether git clone succeeded before returning the directory. If clone fails, subsequent Push-Location/commands will error in less actionable ways; capture the result/exit code and throw a clear error when cloning fails.

Suggested change

git clone "https://github.com/$Owner/$Repo.git" $dir 2>&1 | Out-Null

$cloneOutput = git clone "https://github.com/$Owner/$Repo.git" $dir 2>&1

if ($LASTEXITCODE -ne 0) {

throw "Failed to clone repository '$Repo' into '$dir'. git exited with code $LASTEXITCODE.`nOutput:`n$cloneOutput"

}

Copilot · 2026-03-10T18:33:32Z

+        $url = gh pr create --repo "$Owner/$Repo" --base main --head $branch --title $msg --body $prBody 2>&1
+        $PrUrl.Value  = "$url"
+        # Extract PR number from URL
+        $PrNumber.Value = ($url -replace ".*/pull/", "").Trim()
+        Write-Host "  PR: $url"
+    } finally { Pop-Location }
+}


PR number parsing is brittle here: gh pr create output can include extra text/newlines, and the regex replacement may produce a non-numeric value. Prefer retrieving the PR number via structured output (gh JSON/query options) or by calling gh pr view on the created URL/branch to reliably obtain .number.

Suggested change

$url = gh pr create --repo "$Owner/$Repo" --base main --head $branch --title $msg --body $prBody 2>&1

$PrUrl.Value = "$url"

# Extract PR number from URL

$PrNumber.Value = ($url -replace ".*/pull/", "").Trim()

Write-Host " PR: $url"

} finally { Pop-Location }

}

$prInfo = gh pr create --repo "$Owner/$Repo" --base main --head $branch --title $msg --body $prBody --json number,url | ConvertFrom-Json

$PrUrl.Value = $prInfo.url

$PrNumber.Value = [string]$prInfo.number

Write-Host " PR: $($PrUrl.Value)"

} finally { Pop-Location }

}

}

Copilot · 2026-03-10T18:33:33Z

+    $title = Get-Rotating $issueTitles $Seed
+    $body  = Get-Rotating $issueBodies $Seed
+    $url = gh issue create --repo "$Owner/$Repo" --title $title --body $body 2>&1
+    Write-Host "  Issue: $url"


gh issue create failures won’t be caught by try/catch in Windows PowerShell unless you check the exit code. As written, errors captured into $url may be printed as if it were a valid issue URL. Validate $LASTEXITCODE and fail with a clear message when gh returns non-zero.

Copilot · 2026-03-10T18:33:34Z

+    $body = $reviewBodies[(Get-Date).DayOfYear % $reviewBodies.Count]
+    gh pr review $PrNumber --repo "$Owner/$Repo" --approve --body $body 2>&1 | Out-Null
+    Write-Host "  Approved PR #$PrNumber"


gh pr review can fail (auth, missing permissions, branch protections), but the script suppresses all output and doesn’t check $LASTEXITCODE. That can result in “Approved PR” being printed when no approval happened; check exit code and surface stderr/stdout when the command fails.

Copilot · 2026-03-10T18:33:34Z

+        git commit -m $msg 2>&1 | Out-Null
+        git push -u origin $branch 2>&1 | Out-Null
+        $prBody = "Automated maintenance PR - $(Get-Date -Format 'yyyy-MM-dd')`n`n- Routine log update`n- Part of daily maintenance cycle"
+        $url = gh pr create --repo "$Owner/$Repo" --base main --head $branch --title $msg --body $prBody 2>&1
+        $PrUrl.Value  = "$url"


In this PR flow, failures from git switch/commit/push and gh pr create won’t be caught reliably in Windows PowerShell, and output is mostly suppressed. This can leave a branch pushed without a PR (or vice versa) while the script continues. Check $LASTEXITCODE after each external command and abort/cleanup when a step fails.

Copilot · 2026-03-10T18:33:34Z

+Write-Host ""
+Write-Host "=== daily-activity.ps1 | $(Get-Date -Format 'yyyy-MM-dd HH:mm') ==="
+Write-Host ""
+


This script assumes git and gh are installed and authenticated, but it doesn’t validate prerequisites before starting. Add explicit checks early (e.g., Get-Command git/gh and gh auth status) so the scheduled task fails fast with actionable output.

Suggested change

# ─── Prerequisite checks: git, gh, and gh auth ───────────────────────────────

try {

Get-Command git -ErrorAction Stop | Out-Null

} catch {

Write-Error "Required tool 'git' was not found in PATH. Please install Git and try again."

exit 1

}

try {

Get-Command gh -ErrorAction Stop | Out-Null

} catch {

Write-Error "Required tool 'gh' (GitHub CLI) was not found in PATH. Install it from https://cli.github.com/ and try again."

exit 1

}

try {

gh auth status 2>&1 | Out-Null

} catch {

Write-Error "GitHub CLI is not authenticated. Run 'gh auth login' to authenticate, then re-run this script."

exit 1

}

Copilot · 2026-03-10T18:33:34Z

+param(
+    [string]$ScriptPath = "C:\Users\cashh\zakiscoding\daily-activity.ps1",
+    [string]$TaskName   = "GitHubDailyActivity",
+    [int]$Hour          = 10,
+    [int]$Minute        = 0
+)
+
+$ErrorActionPreference = "Stop"
+
+# Resolve absolute path
+$ScriptPath = (Resolve-Path $ScriptPath).Path
+


The default $ScriptPath is hard-coded to a specific local user path (C:\Users\cashh...). This will fail for other machines and makes the script non-portable; prefer defaulting to the daily-activity.ps1 located alongside this script (e.g., based on $PSScriptRoot) and only Resolve-Path after validating it exists.

chore: add daily GitHub activity automation scripts

c8d9faf

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

Copilot started reviewing on behalf of zakiscoding March 10, 2026 18:27 View session

Copilot AI reviewed Mar 10, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: add daily GitHub activity automation#121

chore: add daily GitHub activity automation#121
zakiscoding wants to merge 1 commit intomainfrom
chore/daily-activity-automation

zakiscoding commented Mar 10, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Copilot AI Mar 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

-            git clone "https://github.com/$Owner/$Repo.git" $dir 2>&1 | Out-Null
+            $cloneOutput = git clone "https://github.com/$Owner/$Repo.git" $dir 2>&1
+            if ($LASTEXITCODE -ne 0) {
+                throw "Failed to clone repository '$Repo' into '$dir'. git exited with code $LASTEXITCODE.`nOutput:`n$cloneOutput"
+            }

+# ─── Prerequisite checks: git, gh, and gh auth ───────────────────────────────
+try {
+    Get-Command git -ErrorAction Stop | Out-Null
+} catch {
+    Write-Error "Required tool 'git' was not found in PATH. Please install Git and try again."
+    exit 1
+}
+try {
+    Get-Command gh -ErrorAction Stop | Out-Null
+} catch {
+    Write-Error "Required tool 'gh' (GitHub CLI) was not found in PATH. Install it from https://cli.github.com/ and try again."
+    exit 1
+}
+try {
+    gh auth status 2>&1 | Out-Null
+} catch {
+    Write-Error "GitHub CLI is not authenticated. Run 'gh auth login' to authenticate, then re-run this script."
+    exit 1
+}

Conversation

zakiscoding commented Mar 10, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants