Skip to content

chore: remove extensionless MAINTAINERS duplicate - #91

Merged
hyperpolymath merged 1 commit into
mainfrom
chore/dedupe-maintainers
Aug 26, 2026
Merged

chore: remove extensionless MAINTAINERS duplicate#91
hyperpolymath merged 1 commit into
mainfrom
chore/dedupe-maintainers

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Removes the extensionless MAINTAINERS, superseded by MAINTAINERS.adoc.

This isn't only a duplicate — the removed file was wrong. It carried:

  • no SPDX header
  • maintainership attributed to "Metadatastician / @metadatastician"

while MAINTAINERS.adoc carries the CC-BY-SA-4.0 header and correctly names Jonathan D.A. Jewell as Lead Maintainer. It is scaffold boilerplate — byte-identical across 37 of 40 repos that had it, the other 3 trivial variants.

Owner-directed 2026-08-26. Raised as a PR because this repo's ruleset requires pull requests and verified signatures, which a direct API commit cannot satisfy.

🤖 Generated with Claude Code

Scaffold boilerplate superseded by MAINTAINERS.adoc. The removed file
carried no SPDX header and attributed maintainership to
'Metadatastician / @metadatastician'; MAINTAINERS.adoc carries the
CC-BY-SA-4.0 header and names Jonathan D.A. Jewell as Lead Maintainer.

Owner-directed 2026-08-26. Done via PR because these repos' rulesets
require pull requests and verified signatures.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@hyperpolymath
hyperpolymath merged commit 6465c0e into main Aug 26, 2026
19 of 22 checks passed
@hyperpolymath
hyperpolymath deleted the chore/dedupe-maintainers branch August 26, 2026 13:01
@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 49429938-77b7-4cfd-a6e5-794e36fab6d6

📥 Commits

Reviewing files that changed from the base of the PR and between 849d011 and 7d98df0.

📒 Files selected for processing (1)
  • MAINTAINERS

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Removed maintainer information, procedures, responsibilities, expectations, and update metadata from the project documentation.

Walkthrough

The pull request removes the MAINTAINERS file and all related maintainer information. No exported or public entities change.

Changes

Cohort / File(s) Summary
Maintainer information removal
MAINTAINERS
Removes maintainer procedures, responsibilities, expectations, and update metadata.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A rabbit checks the empty file,
Then hops along the leafy mile.
No maintainer notes remain,
The burrow rests without a chain.
The branch is clean, the work is done.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gitar-bot

gitar-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

Gitar

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

The review of this pull request confirms the successful removal of the redundant extensionless MAINTAINERS file. This action centralizes maintainership information within the existing MAINTAINERS.adoc file, resolving documentation discrepancies and removing outdated content.\n\nNo security vulnerabilities, architectural concerns, or logic errors were surfaced during the analysis. The project continues to meet all quality standards, and the intended cleanup has been implemented correctly in accordance with the requirements.

Test suggestions

  • Verify the MAINTAINERS file is successfully deleted from the repository structure.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

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