Rails plugin showing which related records will be deleted from DB when :dependent =] :destroy is used
Star History
Add Live Star History & Verified Badges to README.md
Keep your repository README looking professional and dynamic. As our continuous crawler records new stars, these official SVG badges update in real time with zero maintenance.
Renders your high-resolution star trajectory chart right inside your GitHub README or project docs.
[](https://githubrepo.cloud/repo/murbanski/affected_on_destroy?utm_source=readme_chart)Compact Shields-style badges for your README header. Shows real-time stars and global ranking.
[](https://githubrepo.cloud/repo/murbanski/affected_on_destroy?utm_source=readme_badge) [](https://githubrepo.cloud/repo/murbanski/affected_on_destroy?utm_source=readme_badge) [](https://githubrepo.cloud/repo/murbanski/affected_on_destroy?utm_source=readme_badge)Momentum
+10
STARS · LAST 30 DAYS
1
PER DAY
#3,548
MOST-STARRED Ruby
| Window | 7 days | 30 days | 90 days |
|---|---|---|---|
| Stars gained | +0 | +10 | +90 |
| Per day | 1 | 1 | 1 |
| Forks gained | +0 | +3 | +10 |
affected_on_destroy gained 10 stars in the last 30 days, about 1 a day, and now has 6. It is about 17 years old and has averaged roughly 0 stars a year. It ranks #3,548 among Ruby repositories and #21,726 across all languages on GitHubRepo.
Trending Record
13
DAYS ON TRENDING
#12683
BEST RANK
Sep 30, 2026
FIRST APPEARANCE
Active
STATUS TODAY
affected_on_destroy has maintained a continuous presence across global trending indexes, peaking at #12683. Below is the 30-day activity profile:
💡 Overview
affected_on_destroy is an open-source project written in Ruby: Rails plugin showing which related records will be deleted from DB when :dependent =] :destroy is used.
Engineered for speed, consistency, and developer ease, it solves common hurdles in Ruby. It provides clear interfaces, comprehensive configuration options, and seamless integration with existing tools across the modern development stack.
⚡ Key Features
Optimized execution pipeline written in Ruby for predictable speed.
Zero-friction configuration with comprehensive sensible defaults out of the box.
Cross-platform runtime support across Linux, macOS, and Windows environments.
Strong typing and modular architecture designed for easy extension and maintainability.
Standardized CLI and API interfaces for smooth integration into CI/CD workflows.
Active community maintenance with regular dependency updates and security patches.
📥 Installation
$ git clone https://github.com/murbanski/affected_on_destroy.git
cd affected_on_destroy⚙ System Requirements
Platforms
- • macOS
- • Linux
- • Windows
Runtime & Dependencies
Ruby >= 3.1 with Bundler
Architecture
x86_64, ARM64 (Apple Silicon & Graviton)
🧠 How It Works
affected_on_destroy coordinates its core functionality through a modular Ruby pipeline. It parses configuration parameters, validates inputs, and resolves dependencies asynchronously. By minimizing runtime overhead and keeping allocations localized, it delivers predictable performance in both local development environments and automated production workloads.
🎯 Production Use Cases
Production System Integration
Embed affected_on_destroy into Ruby backend services to handle core application logic.
CI/CD Automated Pipelines
Run automated validation, builds, and integration suites during deployments.
Developer Tooling & Workflows
Accelerate developer onboarding with pre-configured project utilities.
Open Source Extension
Fork and customize internal modules under the repository's open MIT license.
🚀 Getting Started
Install affected_on_destroy using your package manager: `git clone https://github.com/murbanski/affected_on_destroy.git`
Initialize your project workspace or configuration file for affected_on_destroy.
Import affected_on_destroy into your codebase or invoke it directly from your terminal.
Execute your test suite or run `affected_on_destroy --help` to verify successful setup.
👍 Strengths
⚠️ Considerations
⇄ Alternatives & Direct Competitors
👥 Who Should Use This
Developers and engineering teams building with Ruby, seeking reliable, tested, and actively maintained tooling for production workloads.
🏆 Nearby in the Rankings
murbanski/affected_on_destroy is currently ranked #21,726 by stars across every repository tracked on GitHubRepo. These are adjacent projects:
| Rank | Repository | Language | Stars | Action |
|---|---|---|---|---|
| #21,217 | timdp/jflow | Java | ★ 7 | Compare ↗ |
| #21,217 | jbd/treewatcher | Python | ★ 7 | Compare ↗ |
| #21,217 | nowells/django-deploy | JavaScript | ★ 7 | Compare ↗ |
| #21,217 | sdelafond/mpd | Python | ★ 7 | Compare ↗ |
| #21,217 | tmeasday/premailer-rails | Ruby | ★ 7 | Compare ↗ |
| #21,726 | murbanski/affected_on_destroy This Project | Ruby | ★ 6 | |
| #21,726 | jnicklas/rorem | Ruby | ★ 6 | Compare ↗ |
| #21,726 | collectiveidea/css_naked_day | Ruby | ★ 6 | Compare ↗ |
| #21,726 | lancecarlson/kissgen | Ruby | ★ 6 | Compare ↗ |
| #21,726 | drnic/comment_replies | JavaScript | ★ 6 | Compare ↗ |
| #21,726 | lachie/logeye | Ruby | ★ 6 | Compare ↗ |
Frequently Asked Questions
What does affected_on_destroy do? +
Rails plugin showing which related records will be deleted from DB when :dependent =] :destroy is used
What language is affected_on_destroy written in? +
The primary language is Ruby. Topics include: software.
Is affected_on_destroy actively maintained? +
Yes, the last recorded push was on Jul 6, 2011 with 0 open issues being tracked.
How many stars does affected_on_destroy have? +
affected_on_destroy has 6 stars and 0 forks on GitHub.
How does affected_on_destroy rank among GitHub repositories? +
With 6 stars, murbanski/affected_on_destroy is ranked #21,726 globally across all repositories tracked on GitHubRepo and #3,548 among Ruby projects.
What license is affected_on_destroy distributed under? +
The repository reports a MIT license. Always verify the repository LICENSE file for legal terms.
