4 ms·

I think the success of such a workflow says a lot of positive things both about drewdevault and git. With respect to git, this is yet another successful workfl

I think the success of such a workflow says a lot of positive things both about drewdevault and git. With respect to git, this is yet another successful workflow conducted through git. While git may have its flaws, one cannot deny that many different workflows are enabled by it. And with respect to this particular workflow, I think it says that drewdevault makes largely self-contained commits with good commit messages and that constantly work. I have been on projects using branched development with people who sometimes make commits that break things, but that then fix them in other commits, with a does-it-really-matter-before-it's-merged-anyway attitude. And I have been on projects where the default commit message is absolutely lousy. (And I am currently involved in a project where both of these are true). But to be able to successfully rebase and reorder and cherrypick commits says a lot to me about highly disciplined organization. I would expect many workflows to be enabled by such habits.

leejo 6y ago
> I think the success of such a workflow says a lot of positive things both about drewdevault and git. There's a massive flaw in this approach if the repo is not private (collaboration is mentioned in the post in terms of "review some incoming patches") in that you can't push works in progress to the remote as you are doing it all in master. If you did push those then when you tidy it up you will cause problems for other collaborators. If you can't push WIP out then you have the only copy, and you're losing some of the distributed advantages of git: distributed backups of your WIP changes being one of those. > But to be able to successfully rebase and reorder and cherrypick commits says a lot to me about highly disciplined organization. Yeah, rebases and cherry-picks are great features. Just use branches as the starting point.
Hamuko 6y ago
>While git may have its flaws, one cannot deny that many different workflows are enabled by it. Eh. I can use an iPad as a cutting board, but I'm not going to put that down as one of the iPad's achievements.

leejo 6y ago

> I think the success of such a workflow says a lot of positive things both about drewdevault and git. There's a massive flaw in this approach if the repo is not private (collaboration is mentioned in the post in terms of "review some incoming patches") in that you can't push works in progress to the remote as you are doing it all in master. If you did push those then when you tidy it up you will cause problems for other collaborators. If you can't push WIP out then you have the only copy, and you're losing some of the distributed advantages of git: distributed backups of your WIP changes being one of those. > But to be able to successfully rebase and reorder and cherrypick commits says a lot to me about highly disciplined organization. Yeah, rebases and cherry-picks are great features. Just use branches as the starting point.

Hamuko 6y ago

>While git may have its flaws, one cannot deny that many different workflows are enabled by it. Eh. I can use an iPad as a cutting board, but I'm not going to put that down as one of the iPad's achievements.