By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code written by Claude will actually have a warning sigil
-
@JamesWidman @nick apple's absurd litigousness pays off possibly for possibly the first time I can think of
-
@lanodan @nick @mcc that's not true.. they can and historically have used GCC, just preferred to migrate when they could.
freebsd changed from gcc to clang as default for main architectures in 2012 but didn't stop shopping gcc until 2020.
openbsd moved to clang in 2018-2020
nerbsd still uses gcc as default
-
-
@bmartin427 github is basically now a website-sized dark pattern to opt you into copilot without your knowledge
@mcc @bmartin427
Can one block Copilot in the same manner? -
@mcc @bmartin427
Can one block Copilot in the same manner?@bloognoo @bmartin427 No, I'm not sure if it leaves the co-authored-by tags or not but significantly GitHub special case made the "copilot" account unblockable
-
@bloognoo @bmartin427 No, I'm not sure if it leaves the co-authored-by tags or not but significantly GitHub special case made the "copilot" account unblockable
@mcc @bmartin427
Bah. Thank you -
@JamesWidman @mcc @nick yea its only a matter of rebasing the fork with upstream
-
@mcc oh no
-
@mcc oh no
-
@mcc oh no
-
@porglezomp @lanodan @nick a nice thing about the block warning is assuming microsoft did not code it in an absurd way, the block warning surely applies only to commits in the past of the current branch.
this would be improved if github had not exempted the copilot bot from blocks. they did exempt it from blocks, and if you look in the github feedback forum there's a feature request from me for the day they did it asking them to not-exempt it. oh well…
@mcc @porglezomp @lanodan @nick The block warning predates Microsoft, at least their active control if not their ownership of GitHub entirely. AIUI it's thanks to @CoralineAda.
