[workshop-sync] workshop/side-quest-20-01-memory-patterns.md: invalid `ttl` field and inaccurate repo-memory storage description
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- documentation
Research direction
Start with workshop/side-quest-20-01-memory-patterns.md and compare its ttl, repo-memory, and permissions statements against the linked cache-memory and repo-memory references. For the permission callout, locate the relevant compiled lock file and generated push job before changing the guidance. The page is done when all three claims match the documented behavior, including cache eviction and branch-based storage.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-20-01-memory-patterns.md (reviewed against gh-aw v0.92.0 docs)
Problems
-
ttlis not acache-memoryfield. The frontmatter example and field table use:ttl: 7d— How long to keep cached data without a refresh... Common values:1d,7d,30d.The cache-memory reference documents only
keyandretention-days(1-90).retention-dayscontrols uploaded artifact retention only and does not extend cache lifetime. GitHub Actions evicts unused cache entries after 7 days regardless. -
repo-memoryis not "a file committed to your repository". The page says:repo-memorybacks a memory slot with a JSON file committed directly to your repository. The agent reads the file at the start of each run and commits an updated version at the end.The repo-memory reference says it stores files on a dedicated Git branch (default
memory/default, mounted at/tmp/gh-aw/repo-memory-default/). The compiler auto-commits and pushes after the run. Files can be any allowed type, not just one JSON file. The table row "A file committed to your repository" and the "survives a repository clone" scenario should be reviewed for the same reason, since a branch needs to be fetched. -
The
contents: writeclaim is not supported by the docs. The[!IMPORTANT]callout saysrepo-memoryrequirescontents: writein the workflow'spermissions. The reference doesn't state this, because the compiler generates the push job. Please verify against a compiled lock file and fix or remove the callout.
Suggested fix
- Replace
ttl: 7dwithretention-days: 7(or remove it), and rewrite the field-table row to describe artifact retention only. Say that cache lifetime is governed by Actions eviction (about 7 days unused). - Describe repo-memory as Git-branch storage (
memory/default) with unlimited retention. - Re-verify and correct the permission callout.
Other files in this run
side-quest-21-01-sub-agent-syntax.md and side-quest-22-01-failure-modes.md had no blocking issues. Optional improvement for 21-01: mention the explicit ## end agent: \name`` marker.
Generated by 🔍 Workshop Sync Check · copilot · auto · 25.6 AIC · ⌖ 0.554 AIC · ⊞ 9.2K · ◷
- expires on Oct 18, 2026, 1:33 PM UTC
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 36
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 18
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from githubnext/gh-aw-workshop
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
githubnext/gh-aw-workshop#4824 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 84/100
githubnext/gh-aw-workshop#4803 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-workshop#4802 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4800 ·
Maintainers usually reply within 1 day
-
documentation guidelines
Difficulty 1/5 Under an hour Newbie friendliness 90/100
githubnext/gh-aw-workshop#4670 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Place search spins forever when nominatim failsPossibly taken @jgt87 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anvaka/city-roads#213 ·
-
mobile UX
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
jellyfin/jellyfin-web#8685 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SchemaStore/schemastore#6535 ·
Maintainers usually reply within 1 day
-
enhancement good first issue helia storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QMeshPy/distributed-quantum#53 ·
Maintainers usually reply within 1 day