Repository navigation
chore: move repo config under .dz/ - #424
Merged
Merged
Conversation
Contributor
Author
✅ Reviewed — nothing blocking0 actionable comment(s) · grounded on your code |
Contributor
Author
There was a problem hiding this comment.
Review summary — 4 file(s), 0 finding(s).
Updates scheduled brief paths to .dz/schedules/ and explicitly configures branch cleanup and scout survey settings. No merge-blocking defect is demonstrated by the supplied diff.
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the maintainer-agent config under
.dz/so the repo root stays readable:.dz/briefs/health.md→.dz/schedules/health.md.dz/briefs/improve.md→.dz/schedules/improve.md.dz/briefs/release-due.md→.dz/schedules/release-due.md.dz/maintainer/maintainer.yml: everybrief_file:under.dz/briefs/now points at.dz/schedules/, the one brief home.dz/maintainer/maintainer.ymlalso gains the current template'sbranches:,scout:A moved file keeps identical content, except the policy's appended template blocks below.
The Contents API returned a new blob sha for each write and the consumer asserted it is
exactly the planned one before opening this PR, so nothing was re-encoded.
Each added block (
branches:,scout:) writes out a value the platform already applies when thekey is absent: the policy parsed with the block is identical to the policy parsed without it,
and the consumer checked that before proposing it, so nothing that runs changes. The blocks
are here so the knob is visible and editable. They are appended below the existing text;
no existing key or comment was rewritten.
Not interested? Just close this PR.