Repository navigation
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
| - **Go command test** (`cmd/**/*_test.go` with `httpmock`) — full CLI wiring | ||
| end to end, but with a stubbed resolver so it stays deterministic. Runs in | ||
| the blocking `test` CI job with no token. Reach for this to prove the | ||
| the blocking `go-test` CI job with no token. Reach for this to prove the |
There was a problem hiding this comment.
🛠️ Find the Go check: The old job name could send Copilot looking for a check identifier that is not defined. The workflow names the job go-test; the command tests still run there without a supplied API token.
| into the repository, then run `gh actions-lock` once so the new workflow is locked too. It runs | ||
| `gh actions-lock --verify` on pull requests, pushes to `main`, and a weekly schedule that catches | ||
| re-pointed tags. The job's `GITHUB_TOKEN` reads public actions and the repository itself; actions | ||
| `gh actions-lock --verify` on pull requests and pushes to `main`. The job's `GITHUB_TOKEN` reads |
There was a problem hiding this comment.
🛠️ Avoid assuming weekly checks: The old claim could make Copilot rely on verification after repository activity stops. The copied workflow triggers only on pull requests and pushes to main; those checks remain, but the template supplies no weekly run.
|
|
||
| ## Learn more | ||
|
|
||
| To diagnose a slow online run, add `--profile <dir>` and read the completed run's |
There was a problem hiding this comment.
🛠️ Use recorded performance data: A help pointer alone leaves Copilot to derive timing and request counts from debug logs. For slow online runs, the existing profiler writes phase timings on completion and instrumented request counts and latency, avoiding manual log counting without replacing the reproduction.
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are identified, and the documentation updates align the guidance with current CI workflows and profiling capabilities.
No open issues 🎉
What changed in this PR
Updates repository guidance to match the current CI workflows and document built-in profiling for diagnosing slow online runs.
Changes:
- Removes the outdated weekly-schedule claim from lockfile verification guidance.
- Corrects the Go test job name to
go-test. - Documents
--profile <dir>output for analyzing phases, request counts, and latency.
This pull request is ready to be approved.
| File | Description |
|---|---|
skills/gh-actions-lock/SKILL.md |
Updates verification workflow documentation and adds profiling guidance. |
AGENTS.md |
Corrects the documented blocking Go test CI job name. |
Review effort: Lite (auto)
🧠 How this helps Copilot
Copilot could assume the copied verification workflow checks for changes every week or look for the Go tests under the wrong check name. This guidance points to the checks that actually run and shows how to use the built-in performance summary instead of manually counting requests in debug logs when an online run is slow.
Automated details
Source:
curate-memoriesDream, analyzingmainat90ae563.