Repository navigation
Conversation
The root .maintainer.yml is the legacy location; the platform reads .dz/maintainer/maintainer.yml first and is retiring the root fallback. The pr.human_merge path that held the policy file now names its new home, so an edit to the policy still waits for a human merge. Every other value is unchanged (auto_merge: true, explicit). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Needs a human: dinndev2/adminer #40 is waiting for your OK to merge. A maintainer merge decision holds this PR: an ask waiting for your answer — a PR in a category the repository asks to approve first (a first-time contributor, a major dependency bump or a large PR, named in the details), a green PR that matched the repository's human-merge rule (the matched pattern is named in the details), or a re-ask raised because a new commit landed after you approved an earlier head — or your skip. It is in your approvals list: approve it there and the platform merges this head, or merge it yourself. 🤖 Posted by developerz.ai — an automated agent, not a human. |
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.
What
Move the legacy root
.maintainer.ymlto.dz/maintainer/maintainer.yml, the current developerz.ai config layout. Thepr.human_merge.pathsentry that held the policy file now names its new path.Why
This is one of the last enabled repos that still uses only the root file. developerz.ai reads
.dz/maintainer/maintainer.ymlfirst and falls back to the root file only when the.dz/path returns a 404. The fallback is being deleted (developerz.ai plan 101 slice 27), and once it is gone this repo would lose its policy unless it is moved first.The effective policy does not change:
pr.auto_merge: trueis already explicit, so the free-tier opt-in still holds. The platform parses the file the same way at either path.human_merge.paths: [.maintainer.yml]. Left as it was, an edit to the moved policy file would no longer be held for a human merge. It now lists.dz/maintainer/maintainer.yml, so that hold stays in place.Changes
.maintainer.yml->.dz/maintainer/maintainer.yml(git mv)pr.human_merge.paths:.maintainer.yml->.dz/maintainer/maintainer.ymlVerification
bun run policy-clifrom developerz.ai:okon the moved file.origin/main) and new files with@developerz/policyparseYaml. Both are valid.pr.auto_mergeistruein both and set explicitly in both, andauto_merge_scopeisanyin both. Onlyhuman_merge.pathsdiffers, and only by the renamed entry.git grepfound no other reference to.maintainer.ymlin the repo (CI, scripts, docs).main.🤖 Generated with Claude Code