redhat-developer / redhat-developer/rhdh-fullsend
GHA observability: inline transcript and run summary
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 2
- Forks
- 7
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 8
Description
Two gaps in GitHub Actions observability for fullsend agent runs.
1. Agent transcript not visible inline in GHA logs
Currently requires gh run download <run-id> --name fullsend-<agent> to see what happened. A post-script step could stream key transcript sections into the GHA step output.
2. No summary in GHA step output
Hard to see what the agent did at a glance. A post-script step could extract key actions (files changed, commands run, result) from the transcript and write them to $GITHUB_STEP_SUMMARY.
Migrated from docs/known-issues.md
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub Actions post-script and the transcript artifact handling for fullsend agent runs. Trace how downloaded transcripts are produced, then define the key sections and actions to expose in step output. Done means the transcript is visible inline and a concise files, commands, and result summary is written to $GITHUB_STEP_SUMMARY.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100