Activity check

[ampelectrecuted]

@OmniBlocks/coders please reply to this issue to verify this repo is active

[traycerai]

Warning

Rate limit exceeded. Please try after 518272 seconds.

[supervoidcoder]

how the frick did you even bulk create issues ACROSS REPOS

@coderabbitai

HOW

is there a way to bulk ccloes them too because why did this even get created

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get details about issue #5 to understand what happened
gh issue view 5 --json title,body,author,createdAt,labels,comments --repo OmniBlocks/extensions

Length of output: 1337

---

🏁 Script executed:

#!/bin/bash
# Search for similar "Activity check" issues across OmniBlocks repos
gh search issues "Activity check org:OmniBlocks" --json title,repository,author,createdAt,number --limit 50

Length of output: 13994

---

@supervoidcoder - I need to clarify: CodeRabbit did NOT create these issues!

Looking at the data, all 23 "Activity check" issues across your OmniBlocks repositories were created by the user @8to16 on January 2, 2026, between 20:19-20:20 UTC. They were all created within about a 30-second window asking "@OmniBlocks/coders" to reply to verify the repos are active.

Here are the affected repositories:

• telewarp, NotebookWriter, OmniBlocks-Paint, OmniText, Calculator, desktop, screen-recorder, demo-repository, UltimateNotebook, extensions, OmniBlocks-Boxy, Notebook, BoxyCPU, omniblocks-website, monorepo, .github, omniblocks.github.io, math, games, omniblocks, simple-analytics, BoxyAI, vmtest

---

Bulk Closing

Yes, I can help you bulk close these issues, but this is a destructive operation. Before I proceed, I need to confirm:

1. Are you a repository maintainer with the authority to bulk close these issues?
2. Do you want to close all 23 "Activity check" issues created by @8to16?
3. Should I add a closing comment explaining why they're being closed?

If you confirm, I can generate a script using GitHub CLI to close them all at once.

[supervoidcoder]

@coderabbitai

no i didn't mean you made them, @8to16 just spammed like every single repo with this exact issue title and body across all 33 repos in the org

[coderabbitai]

@supervoidcoder - Got it, thanks for clarifying! Yes, @8to16 definitely spammed your organization with these "Activity check" issues.

I found 23 of these issues in my search, but you mentioned there are 33 repos total in the org. The missing ones might be in private repos I can't see, or the search had limits.

I can help you bulk close all these spam issues. Here's what I can do:

Since you're dealing with spam across multiple repositories, I can generate a script that will:

1. Find all open issues titled "Activity check" created by @8to16 across the OmniBlocks org
2. Close them all with a standard comment (e.g., "Closing spam issue")
3. Optionally lock them to prevent further activity

Would you like me to proceed? Just confirm and I'll generate the bulk-close script for you. This will help clean up all 33 repos at once.

(And for the future, you might want to check @8to16's permissions across the org - they shouldn't be able to create issues if they're going to spam like this!)

[supervoidcoder]

@coderabbitai well it doesn't matter i already cloesd them all

[coderabbitai]

@supervoidcoder - Great! Glad you got them all cleaned up. Sorry about the spam from @8to16 - hopefully they won't do that again. Let me know if you need anything else! 👍

[ampelectrecuted]

@coderabbitai @supervoidcoder it was to make sure the repos were active and still useful because we have just so many, it wasn't out of malice

i did it using gh

[coderabbitai]

@8to16 @supervoidcoder - Thanks for clarifying, @8to16! That makes sense - with 33 repositories in the org, it's definitely important to audit which ones are still active and being maintained.

For future reference, here are some alternative approaches that might work better for repo activity checks without creating issues across all repos:

1. GitHub CLI analytics: Use gh to check last commit dates, open issues, and PR activity:

   gh repo list OmniBlocks --json name,pushedAt,isArchived --limit 100

2. Archive inactive repos: Instead of issues, you could directly archive repos that are no longer active (they remain visible but read-only)

3. Organization discussion: Create a single discussion in a central repo (like .github or omniblocks) asking maintainers to report on their repos

4. Internal tracking: Use a spreadsheet or project board to track repo status without creating public issues

This way you can get the same information without the notification spam across all repos. But I understand the intention was good - just wanted to share some alternatives for next time! 😊

[supervoidcoder]

@8to16 @coderabbitai
well too many repos isn't really a problem, we have a lot but... so what? we aren't such an established project yet and we're nowhere near 1.0 or to a point where we should be letting people know about it as much so it's just not really a problem

[coderabbitai]

@supervoidcoder - That's totally fair! Every project has its own pace and structure. Having multiple repos for experimentation and development during the early stages makes sense - you can always consolidate or archive later if needed. Focus on building what works for your team right now. 👍

If you need anything else, feel free to tag me!