Daily Repo Goal Achiever: Fix typos and add Artifacts Summary workflow#148
Draft
github-actions[bot] wants to merge 2 commits intomainfrom
Draft
Daily Repo Goal Achiever: Fix typos and add Artifacts Summary workflow#148github-actions[bot] wants to merge 2 commits intomainfrom
github-actions[bot] wants to merge 2 commits intomainfrom
Conversation
- Fix typo 'the a step' -> 'a step' in daily-test-improver.md - Fix duplicate step numbering (4, 4, 5, 6, 7, 8) -> (4, 5, 6, 7, 8, 9) in pr-fix.md
This workflow analyzes GitHub Actions artifacts usage across all workflows and provides comprehensive reports with storage optimization recommendations. Source: gh-aw/.github/workflows/artifacts-summary.md Category: Infrastructure/Cost Management General Purpose: Works for any repository with GitHub Actions Key features: - Analyzes artifact usage across all workflows - Calculates storage statistics (count, size, averages) - Provides actionable optimization recommendations - Creates discussion with comprehensive report - Helps manage GitHub Actions storage costs Generalizations made: - Removed gh-aw-specific shared imports (mood.md, reporting.md, safe-output-app.md) - Removed sandbox/firewall settings - Simplified safe-outputs to discussion only - Made schedule more flexible (weekly instead of specific time) - Added clearer documentation for general repositories Files added: - workflows/artifacts-summary.md - docs/artifacts-summary.md - README.md (added entry under Research, Status & Planning Workflows)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses both Phase 1 (consistency checks) and Phase 2 (workflow discovery) of the Daily Repo Goal Achiever task.
Phase 1: Consistency Fixes
Fixed typos and numbering issues found during documentation review:
Issues Fixed
Typo in
workflows/daily-test-improver.md(line 123)"the a step"→"a step"Duplicate step numbering in
workflows/pr-fix.md(lines 45-55)4, 4, 5, 6, 7, 8→4, 5, 6, 7, 8, 9These were identified through systematic review of all workflow and documentation files for typos, grammar issues, and clarity problems.
Phase 2: Workflow Discovery - Artifacts Summary
Added a new general-purpose workflow from Peli's Agent Factory: Artifacts Summary
Source
gh-aw/.github/workflows/artifacts-summary.mdWhy This Workflow is Valuable
Perfect for General Use:
Business Value:
What It Does
Sample Output
Plus insights like:
Generalization Changes
To make this workflow suitable for the general-purpose agentics collection:
Removed:
shared/mood.md,shared/reporting.md,shared/safe-output-app.md)strict: truemodeChanged:
weekly on sunday around 06:00→weekly(more flexible)q-a(more standard)Kept:
Files Added
workflows/artifacts-summary.md- Workflow definitiondocs/artifacts-summary.md- Comprehensive documentationREADME.md- Added to "Research, Status & Planning Workflows" sectionWhy Not Other Candidates?
During evaluation, I also considered:
Artifacts Summary emerged as the best candidate because it solves a universal problem (storage costs) with zero dependencies and maximum generalizability.
Use Cases
Both Phase 1 fixes and Phase 2 workflow addition are included in this single PR to ensure comprehensive repository improvements in one review cycle.