PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
-
@noboilerplate@namtao.com i hoped i can do the same thing with copilot but it showed a text entry instead, sad
@alice @noboilerplate
Copilot reportedly can appear in participant list for PRs despite never partucipating in which may cause false alarms with that approach. -
@alice @noboilerplate
Copilot reportedly can appear in participant list for PRs despite never partucipating in which may cause false alarms with that approach. -
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
Thanks, this saved me from writing a tool to check repositories for their vibe code potential. People who block `claude` might also be interested in blocking `cursoragent` @noboilerplate
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@noboilerplate PSA: If you abandon Github, you don't need to bother about ai
-
Thanks, this saved me from writing a tool to check repositories for their vibe code potential. People who block `claude` might also be interested in blocking `cursoragent` @noboilerplate
@tobilabu @noboilerplate also recommended to block `gemini-code-assist`
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@noboilerplate Annoyingly, this doesn't seem to work if `claude` was tagged as a co-author: https://github.com/rails/rails/commit/546345c8f708bdadc2b3124ddb458673ae34c63d
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@noboilerplate Very nice. (Can confirm that it works.)
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@noboilerplate Thank you for posting this.
-
It also stops claude from making issues or PRs on any of your repos.
I consider this a bonus.
@noboilerplate @robb too bad we can’t do Copilot and Codex’s usernames too…
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@noboilerplate I wish we could have obvious labels for all this stuff people are passing off as their own. Pretty soon, we're going to start using the same garbage in new garbage.
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@noboilerplate this is a great tip thanks to everyone who boosted it
-
@alice @noboilerplate
Copilot reportedly can appear in participant list for PRs despite never partucipating in which may cause false alarms with that approach.@tiredbun @alice @noboilerplate Worse than that: they appear to only do that if the viewer is logged out last I checked, so the maintainer can't easily see that GitHub is disparaging them by claiming copilot's involvement. (I could see that working out rather poorly for them in certain countries with strong anti-defamation laws if the maintainer is "particularly vocal" about not using it)
-
It also stops claude from making issues or PRs on any of your repos.
I consider this a bonus.
@noboilerplate THIS. IS. AWESOME. Great work bringing this to light.
-
It also stops claude from making issues or PRs on any of your repos.
I consider this a bonus.
@noboilerplate
That's an absolute win -
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
That's a great trick. Thank you.
-
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@noboilerplate@namtao.com You guys have a Github account?
-
@noboilerplate@namtao.com You guys have a Github account?
@SuperDicq *sigh* for now
-
@SuperDicq *sigh* for now
@noboilerplate@namtao.com It's pretty easy to move to something better like Codeberg. Git is a free and distributed version management system after all. All you have to do is "git push" to a new repo and your entire history is there.
-
It also stops claude from making issues or PRs on any of your repos.
I consider this a bonus.
@noboilerplate Funny, but the end result is that you're still using github.
