Skip to content

refactor(config): layer the tickets.* settings at every config level - #456

Merged
danielhanold merged 4 commits into
mainfrom
refactor/layer-the-tickets-config-keys-at-every-normal-level-not-just
Nov 11, 2026
Merged

danielhanold merged 4 commits into
mainfrom
refactor/layer-the-tickets-config-keys-at-every-normal-level-not-just

Conversation

@danielhanold

@danielhanold danielhanold commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

↩ Change 0592 — Layer the tickets.* config keys at every normal level, not just the repo

The ticket settings tickets.provider, tickets.site, tickets.project and the five tickets.auto.* switches now layer like any other key (repo-local > repo-committed > global > built-in) instead of being repo-only. A repository cancels a global value by writing "" or false explicitly. A bare null on a string key that accepts empty is still rejected, and the message now names the "" fix.

  • Schema: eight rows move to scopeAny; layering, provenance, cancel, private-repository and visibility-fold tests.
  • stringLeaf: "" hint on null for settings that accept empty.
  • Docs: docs/reference/config-keys.md, .docket.example.yml (plus embedded copy), prose-contract guards.

Review

Reviewed by docket-review-standard: no findings.

Finding Disposition
(none) —

@danielhanold
danielhanold merged commit 4874f44 into main Nov 11, 2026
1 check passed
@danielhanold
danielhanold deleted the refactor/layer-the-tickets-config-keys-at-every-normal-level-not-just branch November 11, 2026 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant