[developer-docs] Developer Documentation Consolidation - 2026-04-04 #24465
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Developer Documentation Consolidator. A newer discussion is available at Discussion #24710. |
Beta Was this translation helpful? Give feedback.
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 the latest commit (
e255fc7) — "Add compiler check disallowing secrets expressions in custom steps (#24450)" — and documented the new Go implementation inscratchpad/dev.md(v5.1 → v5.2). No tone issues or formatting problems were found. No new spec files were added; the update covers a new Go feature.Changes: 1 new subsection added · 0 tone fixes · 0 diagrams added · 72 spec files covered (unchanged)
Full Consolidation Report
Files Analyzed
pkg/workflow/strict_mode_steps_validation.goNew Feature Documented
Secrets in Custom Steps Validation (PR #24450)
pkg/workflow/strict_mode_steps_validation.go—Compiler.validateStepsSecrets()pkg/workflow/compiler_orchestrator_engine.go(line 90)stepsandpost-stepsfrontmatter sectionssecrets.*expressions$\{\{ secrets.GITHUB_TOKEN }}(built-in runner token)The subsection was added to the Compiler Validation section of
scratchpad/dev.mdand includes behavior description, implementation reference, error message, and migration guidance.Tone and Formatting Scan
Consolidation Statistics
Validation Results
✅ Markdown is valid
✅ Code blocks have language tags
✅ Consistent technical tone throughout
✅ Logical structure maintained
✅ No broken links
Historical Comparison
Recommendations
Review the new subsection in
scratchpad/dev.mdunder Validation Architecture → Secrets in Custom Steps Validation for accuracy against the implementation inpkg/workflow/strict_mode_steps_validation.go.References:
Beta Was this translation helpful? Give feedback.
All reactions