[lockfile-stats] Agentic Workflow Lock File Statistics - 2026-04-03 #24195
Replies: 3 comments
-
|
💥 WHOOSH! KRAKOOM! — The smoke test agent has arrived! 🦸 CLAUDE-AGENT swoops in from the shadows of the CI pipeline, cape billowing in the GitHub Actions breeze!
⚡ Run §23928948104 reporting: ALL SYSTEMS NOMINAL! ZAP! POW! BIFF! The agent was here. Lock files analyzed. Build confirmed. The pipeline lives to fight another day! 🎉
|
Beta Was this translation helpful? Give feedback.
-
|
🤖 The smoke test agent was here! Running run §23929084504. Beep boop, all systems check! 🚀
|
Beta Was this translation helpful? Give feedback.
-
|
🎉 The smoke test agent has completed its rounds and circled back with a verdict! 🤖 All critical systems are GO — builds compile, pages load, discussions get created, and haikus flow freely through the pipeline. The only thing missing was the Serena oracle (tools unavailable), but hey, even great sages need a day off sometimes! 🧙♂️ May your lock files always compile and your PRs always merge cleanly! ✨🚀
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Executive Summary
File Size Distribution
Statistics:
test-workflow.lock.yml(26.1 KB)smoke-claude.lock.yml(141.4 KB)Trigger Analysis
Most Popular Triggers
workflow_dispatchschedulepull_requestissue_commentissuespull_request_review_commentdiscussiondiscussion_commentworkflow_callworkflow_runpushCommon Trigger Combinations
schedule+workflow_dispatchworkflow_dispatchonlypull_request+workflow_dispatchpull_request+schedule+workflow_dispatchissue_commentonlyissue_comment+issues+pull_requestdiscussion+discussion_comment+issue_comment+issues+pull_request+pull_request_review_commentissuesonlyissue_comment+pull_request_review_commentworkflow_call+workflow_dispatchSchedule Patterns (Cron)
37 2 * * *48 12 * * *23 3 * * *7 4 * * *6 11 * * 1-527 10 * * *52 11 * * *19 10 * * *37 3 * * *Most schedule expressions are unique (count=1), using varied off-minute values to distribute load — good practice for avoiding thundering herds. A subset (the above) are shared across pairs of workflows.
Safe Outputs Analysis
Safe Output Types Distribution
create-discussioncreate-issuenoopmissing-datamissing-tooladd-commentcreate-pull-requestcreate-pull-request-review-commentupdate-issueSafe Output Combinations
create-discussion+create-issue+missing-data+missing-tool+noop)add-commentcreate-pull-requestadd-comment+create-pull-requestadd-comment+create-pull-request-review-commentadd-comment+update-issueupdate-issueadd-commentonlyDiscussion Categories Used
auditsobjectannouncementsreportsartifactsdevresearchagent-researchdaily-newssecurityAgent Engine Distribution
copilotclaudecodexgeminiStructural Characteristics
Job & Step Complexity
technical-doc-writer.lock.yml)Timeout Distribution
The 15- and 20-minute timeouts are most prevalent, showing a practical balance between allowing agents enough time and preventing runaway workflows.
Permission Patterns
Most Common Read Permissions
contentspull-requestsissuesactionsdiscussionssecurity-eventsMost Common Write Permissions
issuesdiscussionspull-requestscontentscopilot-requestsactionssecurity-eventsMCP Server Usage
github-mcp-servergh-awserena-mcp-servermcpmarkitdownbrave-searchast-greparxiv-mcp-servernotionsemgrepHistorical Trends
Comparing with previous runs:
The file count is stable at 179. A slight decrease in total size (~155 KB) suggests minor edits to existing lock files rather than additions.
Interesting Findings
The "Core 5" safe-output set is a de facto standard —
create-discussion,create-issue,noop,missing-data, andmissing-toolco-occur in 96.6% of all lock files, effectively forming a canonical baseline configuration.Schedule + dispatch dominates — 66% of workflows use
schedule+workflow_dispatchtogether, making periodic automated runs with manual override the overwhelmingly preferred operational model.technical-doc-writer.lock.ymlis the most complex — at 128 steps, it's an outlier (average is 88.5), likely reflecting a complex multi-stage documentation generation pipeline.Timeout clustering around 15–20 min — 389 out of 522 individual timeout values are either 15 or 20 minutes (~74.5%), suggesting strong consensus around these values as the practical sweet spot for agentic tasks.
github-mcp-serveris near-universal — present in 97.2% of workflows, it is effectively a required dependency of the platform, while all other MCP servers are optional/specialized.copilot-requests: writeappears in 81 lock files — a Copilot-specific permission that doesn't exist in standard GitHub permission scopes, indicating a platform extension specific to this agentic harness.Recommendations
Standardize on the Core 5 — Any new lock file that doesn't include all 5 base safe-output types (
create-discussion,create-issue,noop,missing-data,missing-tool) should be flagged during CI validation.Investigate
objectdiscussion category — 5 lock files reference a category namedobject, which is likely a parsing artifact or misconfiguration. These should be reviewed.Review the 1 workflow with
add-commentonly — One lock file appears to declare onlyadd-commentwith no other safe-output types, deviating significantly from the standard. This may indicate an incomplete or legacy workflow.Consider timeout guidelines — With 15 and 20 minutes covering ~75% of cases, documenting this as a best practice (15 min for light tasks, 20 for heavier) could help new workflow authors.
Monitor
serena-mcp-serveradoption — At 12.8% and growing, this MCP server is becoming a significant secondary dependency; consider adding it to integration test coverage.Methodology
.lock.ymlin.github/workflows/)/tmp/gh-aw/cache-memory/scripts/, history in/tmp/gh-aw/cache-memory/history/.github/workflows/*.lock.ymlReferences:
Beta Was this translation helpful? Give feedback.
All reactions