Follow-up to #17, split out from PR #22 (which added git config stack.blockLink to drop the attribution heading link).
#22 covers the heading-link toggle. The remaining enterprise-safe stack-block options from #17 are still open:
Separately, #17 also requests shipping the stack skill with the published npm package — that is independent of the block rendering and should be tracked there or in its own issue.
Minor hardening also noted during review: the git config --get stack.* reads accept exit codes [0,1], so a multi-valued key (set twice) would error (exit 2). Low priority; if addressed, do it consistently across stack.codeHost, stack.trunks, and stack.blockLink.
Follow-up to #17, split out from PR #22 (which added
git config stack.blockLinkto drop the attribution heading link).#22 covers the heading-link toggle. The remaining enterprise-safe stack-block options from #17 are still open:
stack.blockUrl— point the heading at an internal docs URL instead of this project.stack.blockTitle— customize the heading text.#101references in a description can trigger Jira/automation pipelines;blockLink falsedoes not address that since it keeps the references.)Separately, #17 also requests shipping the stack skill with the published npm package — that is independent of the block rendering and should be tracked there or in its own issue.
Minor hardening also noted during review: the
git config --get stack.*reads accept exit codes[0,1], so a multi-valued key (set twice) would error (exit 2). Low priority; if addressed, do it consistently acrossstack.codeHost,stack.trunks, andstack.blockLink.