Add repository safety checks workflow

[Dumken1]

Pull Request Checklist

Branch

• This branch was created from the latest master.
• This work is scoped to one feature, research task, design task, documentation task, experiment, or fix.

Human Learning

• I can explain what changed without relying only on AI output.
• I added or updated a weekly report.
• I added a human learning log if this work involved learning.
• I added a paper note if a paper or technical source shaped the work.

Design And Research

• I added a design outcome if the work changed architecture, flow, data model, interface, or evaluation approach.
• I linked the relevant paper, article, official documentation, or technical source.
• I explained the design decision and alternatives considered.

Verification

• I ran the relevant tests, script, benchmark, or manual check.
• I recorded evidence in the weekly report, benchmark results, screenshots, or notes.
• I ran scripts/verify-contribution.ps1.

AI Use

• I reviewed any AI-generated content before committing it.
• I documented where AI helped if it influenced the work.
• I made the final judgment as the human contributor.

Summary

What changed?
Added a github action workflow

What did you learn?
Base layer Changes

What should the next contributor know?
This is just an automatic merge

Summary by CodeRabbit

• Chores
  • Added automated repository safety checks for pull requests and pushes to the main branch.
  • The new check verifies that a README is present and flags unresolved merge conflict markers before changes are accepted.

[coderabbitai]

Warning

Review limit reached

@Dumken1, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 25 minutes and 5 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5bc978f1-2fa9-4d42-94e5-b1013d69e088

📥 Commits

Reviewing files that changed from the base of the PR and between 9adc4e9 and 94bac1a.

📒 Files selected for processing (1)

• .github/workflows/repository-safety-check.yml

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow file is added that runs on pull_request and push events to master. It checks out the repository, verifies README.md exists, and scans all files (excluding .git) for unresolved merge conflict markers, failing the job if any are found.

Changes

Repository Safety Check Workflow

Layer / File(s)	Summary
Workflow triggers, permissions, and safety job .github/workflows/repository-safety-check.yml	Defines the workflow with contents: read permissions triggered on PRs and pushes to master; job steps check out the repo, assert README.md exists, and use grep to fail if merge conflict markers (<<<<<<<, =======, >>>>>>>) are detected.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through every file,
Sniffing out conflicts with a smile,
No <<<<<<< shall pass my nose,
README must exist — goodness knows!
🐇✨ The repo is safe, off I goes!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a repository safety checks workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch Dumken1-patch-1

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/repository-safety-check.yml:
- Around line 20-21: The checkout step in the repository-safety-check workflow
is persisting the job token in git config by default. Update the existing
actions/checkout@v4 step to disable credential persistence by setting
persist-credentials to false, keeping the change localized to the Checkout
repository step in the workflow.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 584e90b7-b6e5-40b5-9aca-520f84639949

📥 Commits

Reviewing files that changed from the base of the PR and between 432df48 and 9adc4e9.

📒 Files selected for processing (1)

• .github/workflows/repository-safety-check.yml