Блог*
Photo
Кстати, @aviasales, упустили возможность пошутить в духе "Евгений Викторович, если вы так хотели в Беларусь, то куда дешевле было бы купить у нас билет"
😁15💩1
#prog #article
Where are my Git UI features from the future?
Или про то, какие более адекватные высокоуровневые операции стоило бы иметь в Git.
Проекты, про которые я узнал из этой статьи и которые меня впечатлили:
Gitless
git-branchless (shameless plug со стороны автора, но тем не менее)
Where are my Git UI features from the future?
Или про то, какие более адекватные высокоуровневые операции стоило бы иметь в Git.
Проекты, про которые я узнал из этой статьи и которые меня впечатлили:
Gitless
git-branchless (shameless plug со стороны автора, но тем не менее)
GitHub
GitHub - arxanas/git-branchless: High-velocity, monorepo-scale workflow for Git
High-velocity, monorepo-scale workflow for Git. Contribute to arxanas/git-branchless development by creating an account on GitHub.
👍1🖕1
#prog #article
Stacked Diffs Versus Pull Requests
<...>
Before I dig deeply, let me just say I’ve created and merged hundreds of Pull Requests and landed thousands of Diffs. I know both of these workflows in and out. I’m not just some ex-Facebook, Phabricator fan boy pining for the ‘good old days.’ I’ve worked on engineering teams using CVS (oh yes), SVN, Git, and Mercurial. GitLabs, GitHub, Gerrit, and Phabricator. I’ll happily acknowledge that you can get a lot of good work done using any of these. Now, if you want to talk about how to get the most work done — the most productivity per engineer — that’s where I have a strong opinion informed by lots of experience.
<...>
The stacked diff workflow is a clearly higher-throughput workflow that gives significantly more power to engineers to develop code as they see fit.
Inside Facebook, engineering used the branch-oriented workflow for years. They eventually replaced it with the stacked diff workflow because it made engineers more productive in very concrete terms. It also encourages good engineering practices in a way exactly opposite to branching and Pull Requests. [выделение моё]
Stacked Diffs Versus Pull Requests
<...>
Before I dig deeply, let me just say I’ve created and merged hundreds of Pull Requests and landed thousands of Diffs. I know both of these workflows in and out. I’m not just some ex-Facebook, Phabricator fan boy pining for the ‘good old days.’ I’ve worked on engineering teams using CVS (oh yes), SVN, Git, and Mercurial. GitLabs, GitHub, Gerrit, and Phabricator. I’ll happily acknowledge that you can get a lot of good work done using any of these. Now, if you want to talk about how to get the most work done — the most productivity per engineer — that’s where I have a strong opinion informed by lots of experience.
<...>
The stacked diff workflow is a clearly higher-throughput workflow that gives significantly more power to engineers to develop code as they see fit.
Inside Facebook, engineering used the branch-oriented workflow for years. They eventually replaced it with the stacked diff workflow because it made engineers more productive in very concrete terms. It also encourages good engineering practices in a way exactly opposite to branching and Pull Requests. [выделение моё]
🖕1