Repository navigation
chore: move repo config under .dz/ - #37
developerz-ai[bot] wants to merge 11 commits into
Conversation
✅ Reviewed — nothing blocking0 actionable comment(s) · grounded on your code 🤖 developerz.ai — automated review, running on your model and your box. |
There was a problem hiding this comment.
Review summary — 6 file(s), 0 finding(s).
Updates scheduled brief paths and adds explicit branch-retention and scout settings. No concrete defect is established by the supplied diff; moved-file contents and platform default equivalence are not independently verifiable here.
- 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
🤖 developerz.ai review — automated, running on your model and your box. What is this?
|
The developerz.ai bot is closing this pull request: it also changes gate files the merge check cannot machine-prove safe, and a fix round may not revert them. It changes The merge check refused it ( The platform's setup template owns those files, so a fix round may not edit them and the revert cannot be made here. No goal is re-filed for it. The branch 🤖 Posted by developerz.ai — an automated agent, not a human. |
Moves the maintainer-agent config under
.dz/so the repo root stays readable:.dz/briefs/compat.md→.dz/schedules/compat.md.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/briefs/security-release.md→.dz/schedules/security-release.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.
🤖 Opened automatically by developerz.ai (
developerz-ai[bot]), an automated agent, not a human. Not interested? Just close this PR. What is this?