musicmatze  Oct 20

Did you know that the #rust #rustlang project will soon break everyones workflows?

#git #github

Show threadNik | Klampfradler 🎸🚲Oct 20
@musicmatze What?
Show threadmusicmatze  
@nik https://blog.rust-lang.org/inside-rust/2025/10/16/renaming-the-default-branch-of-rust-langrust/
Renaming the default branch of rust-lang/rust | Inside Rust Blog

Want to follow along with Rust development? Curious how you might get involved? Take a look!

Oct 20 at 6:54pmWeb
Show threadNik | Klampfradler 🎸🚲Oct 20
@musicmatze I can't come up with any workflow that will break for me due to this.
Show threadmusicmatze  Oct 20
@nik lucky you.
Show threadNik | Klampfradler 🎸🚲Oct 20
@musicmatze So you are claiming that almost everyone using Rust will be affected by this change? How?
Show threadmusicmatze  Oct 20

@nik I did not specify that it breaks everyones workflow who is "using rust".
I just said "everyones", leaving out which group I mean by that. 😉

IMO branch renames breaks workflows of users of the repository where the rename happens.

Show threadAlejandra 🔜 Rust In ParisOct 20

@musicmatze @nik First saying "everyone" and then stating that everyone doesn't even include that big of a group (only people that work with the main rust-lang/rust repo) is a bit disingenuous.

I work regularly with rust-lang/rust and rust-lang/rust-clippy, have half a dozen scripts that point to those repos for fetching.

The fix? A single line diff, `-master +HEAD`, I really don't see the issue or why you should use the rust hashtag and worry people. Rust user's workflows won't be affected a single bit.

Show threadNate CoxOct 20

@musicmatze @nik

“Everyone using rust” is, surprisingly, actually a subset of “everyone”.

Show threadlaundOct 21
@musicmatze @nik That's an incredibly disingenuous way to go about this, and feels like you're actually just clickbaiting people. and for what? Clicks mean nothing here.