Very cool that GitHub actually put stacks in the UI vs. GitLab's `glab stack`[0] (which looks just like the `gh stack` part of GitHub's thing).
One part that seems like it's going to feel a little weird is how merging is set up[1].
That is, if I merge the bottom of the stack, it'll rebase the others in the stack, which will probably trigger a CI test run. So, if I have three patches in the stack, and I want to merge the bottom two, I'd merge one, wait for tests to run on the other, merge the second vs. merge just those two in one step (though, without having used it, can't be sure about how this'd work in practice—maybe there's some way to work around this with restacking?)
> So, if I have three patches in the stack, and I want to merge the bottom two, I'd merge one, wait for tests to run on the other, merge the second vs. merge just those two in one step
As we have it designed currently, you would have to wait for CI to pass on the bottom two and then you can merge the bottom two in one step. The top of the stack would then get rebased, which will likely trigger another CI run.
Thanks for the callout - we'll update those docs to make it clear multiple PRs can be merged at once.
I’ve been using Ctrl-s for years. Nothing else uses it because it’s historically been used for terminal flow control, but that doesn’t really have much use in a graphical terminal with history and scrollbars and so I’ve never missed it. Has similar two-finger ergonomics to the Ctrl-a bind as well.
edit: oh, and I think Ctrl-space is the keystroke to get a nul character, and vi uses that character to insert the last entered piece of text in insert mode. It looks like Ctrl-@ does the same things, but tmux might not be able to tell the difference either.
Ctrl+s is evil. I can't count how many times I froze my terminal by accident before realizing that Ctrl+q "unfreezes" it. I absolutely support rebinding it.
Same, I used C-a for a while until I found out its default mapping is jumping to the beginning of the line so I rebound tmux prefix to C-Space. Now my only problem is on a few servers where I haven't copied my dotfiles.
> Today, with Git, we're all teaching swarms of agents to use a tool built for sending patches over mailing lists. That's far from what is needed today.
Today, with English, we're all teaching swarms of agents to use a language built from scraps of Norman French and Anglo-Saxon Old English. That's far from what is needed today.
I read the qntm book in Dec. TIL: there's a whole, rad backstory here.
This scene is really arresting, which is how they get you. I kind of coasted through the book on this big idea.
The rest of the book felt like this scene playing out over and over on a bigger scale, with higher stakes, with roles switched around. It's hard to move a plot with this theme.
The book did a commendable job.But I was ready for it to be over when it was over.
This chart shows that the rate of year-over-year, month-by-month change is worse than 2020.
But the number of tech jobs has grown by 12% since April of 2020 (2.34M vs. 2.63M). Heck, there are more tech jobs today than at the beginning of 2022 (2.61M), even.
Job market sucks, trend is bad, but post title is a misnomer for what this chart shows.
(Numbers based on a quick grab BLS.gov data of CES6054151101 (Custom Computer Programming Services) + CES5051800001 (Computing Infrastructure Providers, Data Processing & Web Hosting) + CES6054151201 (Computer Systems Design Services)---couldn't find other ones quickly and gave up :))
> English has a contrast between kinds of clause in which one kind has the standard correspondence between grammatical subject and semantic roles (when a verb denotes an action, the subject standardly corresponds to the agent), and the other switches those roles around.
I've tried to read this sentence so many times. That parenthetical is a doozy.
The sentence isn't that unnatural when you realize that it's full of standard linguistic terms, such as "clause", "subject", "semantic roles", "action", and "agent".
Pick a random sentence from discussion on tax laws or building an npm package, and they will sound just as ridiculous (or even pompous) to outsiders.
Same with Ezra Kline's "Abundance" vs. John Green's "An Abundance of Katherines." But I kinda like swapping in John Green—"Everything is Tuberculosis" was a good read for me this year.
One part that seems like it's going to feel a little weird is how merging is set up[1].
That is, if I merge the bottom of the stack, it'll rebase the others in the stack, which will probably trigger a CI test run. So, if I have three patches in the stack, and I want to merge the bottom two, I'd merge one, wait for tests to run on the other, merge the second vs. merge just those two in one step (though, without having used it, can't be sure about how this'd work in practice—maybe there's some way to work around this with restacking?)
[0]: <https://docs.gitlab.com/cli/stack/>
[1]: <https://github.github.com/gh-stack/guides/stacked-prs/#mergi...>
reply