4 ms·
I think it really depends of the project, the team size... - When I work solo on a project, I do my "daily commit of work". - On an open source project, I squ
by kuon 9y ago
I think it really depends of the project, the team size...
- When I work solo on a project, I do my "daily commit of work".
- On an open source project, I squash my commits at the end into one per "feature" or "issue".
- In a larger team, I usually work in a branch, then I submit the whole branch for review, this let people checkout the branch, test it and review it, without breaking their own workflow. After this, the branch is merged in the format that make the most sense for the project (usually, but not alway, 1 commit per branch is kept).
For the planning thing, I prefer to create issues (even for my own personal project).
- fiatjaf 9y agoNow you're making "planning" seem like a huge deal. No, sometimes you just want to do little change, that's what the article is talking about. In other words: you commit a lot, right? Do you have an issue for each commit? If not, then you're not using "planning" in the same way OP is doing, and your comments about "planning" don't apply.
- kuon 9y agoIf it's not a personal project, I usualy have 1 issue per commit. All my issues have a #close xxx in the comment.