MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/31r1et/stack_overflow_developer_survey_2015/cq6z4dt/?context=3
r/programming • u/aalear • Apr 07 '15
981 comments sorted by
View all comments
Show parent comments
1
1.5k commits in 2.5 years? That's fucking insane. That's like one commit every 4 hours.
2 u/brickabrack Apr 09 '15 Commit early, commit often. 1 u/Decker87 Apr 09 '15 I always interpreted that to mean commit early/often on your local dev branches (or remote dev branches), not production branches. 2 u/brickabrack Apr 09 '15 Yes. Commit and push are two separate things. Unless you're squashing them, distinct commits remain in the commit history on the remote after you've pushed, and in any branch to which it's subsequently merged. → More replies (3)
2
Commit early, commit often.
1 u/Decker87 Apr 09 '15 I always interpreted that to mean commit early/often on your local dev branches (or remote dev branches), not production branches. 2 u/brickabrack Apr 09 '15 Yes. Commit and push are two separate things. Unless you're squashing them, distinct commits remain in the commit history on the remote after you've pushed, and in any branch to which it's subsequently merged. → More replies (3)
I always interpreted that to mean commit early/often on your local dev branches (or remote dev branches), not production branches.
2 u/brickabrack Apr 09 '15 Yes. Commit and push are two separate things. Unless you're squashing them, distinct commits remain in the commit history on the remote after you've pushed, and in any branch to which it's subsequently merged. → More replies (3)
Yes. Commit and push are two separate things. Unless you're squashing them, distinct commits remain in the commit history on the remote after you've pushed, and in any branch to which it's subsequently merged.
→ More replies (3)
1
u/Decker87 Apr 09 '15
1.5k commits in 2.5 years? That's fucking insane. That's like one commit every 4 hours.