Repository navigation
[delight] Delight report 2026-11-20: dependency error clarity and weekly-update metadata #79536
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Delight. A newer discussion is available at Discussion #79818. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Analyzed 8 items across docs, CLI help, workflow messages, and validation code. Overall quality: needs work.
Key finding: the apt dependency error labels its manager as "shell", and the invalid-name error always suggests a requests example. Both mislead apt users.
Quality highlights
--actions-lockincompatibility list matchespkg/cli/compile_validation.go.GH_AW_DEFAULT_*anchor resolves to its heading.Actionable tasks
Task 1: Improve dependency error messages in mcp_scripts_dependencies_validation.go
File to modify:
pkg/workflow/mcp_scripts_dependencies_validation.goCurrent experience: line 132 reports the apt manager as "shell". Line 154 hardcodes
Example: dependencies: [requests]for every package manager.Design principle: clarity and precision. An error should name the right manager and give an example that matches it.
Before
After
User impact: apt users see the wrong manager name and a pip-style example.
Success criteria
pkg/workflow/mcp_scripts_dependencies_validation.gochangedis not pinned to a release tag,invalid dependency name)Scope constraint: single file only.
Task 2: Correct release count in weekly-update description
File to modify:
docs/src/content/docs/blog/2026-10-26-weekly-update.mdCurrent experience: front matter line 3 says "Five releases (v0.93.0–v0.93.5)". The body line 11 says six releases, and v0.93.0 through v0.93.5 is six releases.
Design principle: trust and reliability. Metadata must agree with the body.
Before
After
User impact: listing and SEO previews show a count that contradicts the post.
Success criteria
Scope constraint: single file only.
Deferred
.github/workflows/smoke-test-tools.mdline 60:detected missing tools: {status}uses{status}for run outcome text. The fix needsmake recompile, which rewrites the derived lock file, so it does not fit a single-file task. Tracked in repo memory.docs/src/content/docs/reference/workflow-linters.mdline 170 is missing a space before "Ordinary". Tracked in repo memory.Files reviewed
Metrics
Memory:
findings-2026-11-20.jsonwritten.improvements.jsonupdated with the new task notes.All reactions