▲ 792 ▼ Manager: This task only takes 30 minutes. Why did it take you the whole day? (programming.dev) submitted 2 years ago by hypnotic_nerd@programming.dev to c/programmer_humor@programming.dev 95 comments fedilink hide all child comments
[–] aes@lemm.ee 36 points 2 years ago (2 children) Psst, git add -p permalink fedilink source hideshow 4 child comments replies: [–] Johanno@feddit.de 13 points 2 years ago (1 child) What does this? permalink fedilink source parent hideshow 2 child comments replies: [–] foxymulder@lemmy.ml 39 points 2 years ago (2 children) "patch mode" - Patch mode allows you to stage parts of a changed file, instead of the entire file. This allows you to make concise, well-crafted commits that make for an easier to read history. permalink fedilink source parent hideshow 4 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 14 points 2 years ago (2 children) Highly recommend throwing --patch on any git commands you're used to using. You will have the prettiest, most atomic fkn commit, I'm serious people will love you for it. I mean many people won't care, but the quality folk will notice and approve. permalink fedilink source parent hideshow 4 child comments replies: [–] Johanno@feddit.de 7 points 2 years ago (2 children) We make a singular commit per feature. permalink fedilink source parent hideshow 4 child comments replies: [–] KairuByte@lemmy.dbzer0.com 5 points 2 years ago I always find this hard to follow personally. permalink fedilink source parent [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (1 child) Trunk based, eh? Yeah, we do that on a couple teams where I'm at, too. I like the philosophy, but force pushing the same commit over and over as you're incorporating review feedback is antisocial, especially when you've got devs trying to test your changes out on their machines. permalink fedilink source parent hideshow 2 child comments replies: [–] Omgpwnies@lemmy.world 3 points 2 years ago (1 child) eh, just squash and merge. Feature branch can be messy as long as main is clean permalink fedilink source parent hideshow 2 child comments replies: [–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent [–] oce@jlai.lu 4 points 2 years ago* (1 child) Or just use a good IDE that makes doing atomic commits pretty natural. permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (2 children) I've only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I've never found it worth the trouble personally permalink fedilink source parent hideshow 4 child comments replies: [–] dukk@programming.dev 3 points 2 years ago (1 child) Shout out to Lazygit for letting me stage individual lines permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent [–] oce@jlai.lu 2 points 2 years ago You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It's much more convenient than commands and terminal text editors. permalink fedilink source parent [–] AnarchistArtificer@lemmy.world 3 points 2 years ago Yay, learning! permalink fedilink source parent [–] dukk@programming.dev 7 points 2 years ago* (1 child) Better yet, git commit -p permalink fedilink source parent hideshow 2 child comments replies: [–] sip@programming.dev 6 points 2 years ago uuuuuuuu. and you could do -m to describe the commit. next they'll add --push/-P. perhaps add -r for fetch/rebase then commit. one command to rule them all! 😈 permalink fedilink source parent
[–] Johanno@feddit.de 13 points 2 years ago (1 child) What does this? permalink fedilink source parent hideshow 2 child comments replies: [–] foxymulder@lemmy.ml 39 points 2 years ago (2 children) "patch mode" - Patch mode allows you to stage parts of a changed file, instead of the entire file. This allows you to make concise, well-crafted commits that make for an easier to read history. permalink fedilink source parent hideshow 4 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 14 points 2 years ago (2 children) Highly recommend throwing --patch on any git commands you're used to using. You will have the prettiest, most atomic fkn commit, I'm serious people will love you for it. I mean many people won't care, but the quality folk will notice and approve. permalink fedilink source parent hideshow 4 child comments replies: [–] Johanno@feddit.de 7 points 2 years ago (2 children) We make a singular commit per feature. permalink fedilink source parent hideshow 4 child comments replies: [–] KairuByte@lemmy.dbzer0.com 5 points 2 years ago I always find this hard to follow personally. permalink fedilink source parent [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (1 child) Trunk based, eh? Yeah, we do that on a couple teams where I'm at, too. I like the philosophy, but force pushing the same commit over and over as you're incorporating review feedback is antisocial, especially when you've got devs trying to test your changes out on their machines. permalink fedilink source parent hideshow 2 child comments replies: [–] Omgpwnies@lemmy.world 3 points 2 years ago (1 child) eh, just squash and merge. Feature branch can be messy as long as main is clean permalink fedilink source parent hideshow 2 child comments replies: [–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent [–] oce@jlai.lu 4 points 2 years ago* (1 child) Or just use a good IDE that makes doing atomic commits pretty natural. permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (2 children) I've only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I've never found it worth the trouble personally permalink fedilink source parent hideshow 4 child comments replies: [–] dukk@programming.dev 3 points 2 years ago (1 child) Shout out to Lazygit for letting me stage individual lines permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent [–] oce@jlai.lu 2 points 2 years ago You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It's much more convenient than commands and terminal text editors. permalink fedilink source parent [–] AnarchistArtificer@lemmy.world 3 points 2 years ago Yay, learning! permalink fedilink source parent
[–] foxymulder@lemmy.ml 39 points 2 years ago (2 children) "patch mode" - Patch mode allows you to stage parts of a changed file, instead of the entire file. This allows you to make concise, well-crafted commits that make for an easier to read history. permalink fedilink source parent hideshow 4 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 14 points 2 years ago (2 children) Highly recommend throwing --patch on any git commands you're used to using. You will have the prettiest, most atomic fkn commit, I'm serious people will love you for it. I mean many people won't care, but the quality folk will notice and approve. permalink fedilink source parent hideshow 4 child comments replies: [–] Johanno@feddit.de 7 points 2 years ago (2 children) We make a singular commit per feature. permalink fedilink source parent hideshow 4 child comments replies: [–] KairuByte@lemmy.dbzer0.com 5 points 2 years ago I always find this hard to follow personally. permalink fedilink source parent [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (1 child) Trunk based, eh? Yeah, we do that on a couple teams where I'm at, too. I like the philosophy, but force pushing the same commit over and over as you're incorporating review feedback is antisocial, especially when you've got devs trying to test your changes out on their machines. permalink fedilink source parent hideshow 2 child comments replies: [–] Omgpwnies@lemmy.world 3 points 2 years ago (1 child) eh, just squash and merge. Feature branch can be messy as long as main is clean permalink fedilink source parent hideshow 2 child comments replies: [–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent [–] oce@jlai.lu 4 points 2 years ago* (1 child) Or just use a good IDE that makes doing atomic commits pretty natural. permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (2 children) I've only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I've never found it worth the trouble personally permalink fedilink source parent hideshow 4 child comments replies: [–] dukk@programming.dev 3 points 2 years ago (1 child) Shout out to Lazygit for letting me stage individual lines permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent [–] oce@jlai.lu 2 points 2 years ago You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It's much more convenient than commands and terminal text editors. permalink fedilink source parent [–] AnarchistArtificer@lemmy.world 3 points 2 years ago Yay, learning! permalink fedilink source parent
[–] pomodoro_longbreak@sh.itjust.works 14 points 2 years ago (2 children) Highly recommend throwing --patch on any git commands you're used to using. You will have the prettiest, most atomic fkn commit, I'm serious people will love you for it. I mean many people won't care, but the quality folk will notice and approve. permalink fedilink source parent hideshow 4 child comments replies: [–] Johanno@feddit.de 7 points 2 years ago (2 children) We make a singular commit per feature. permalink fedilink source parent hideshow 4 child comments replies: [–] KairuByte@lemmy.dbzer0.com 5 points 2 years ago I always find this hard to follow personally. permalink fedilink source parent [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (1 child) Trunk based, eh? Yeah, we do that on a couple teams where I'm at, too. I like the philosophy, but force pushing the same commit over and over as you're incorporating review feedback is antisocial, especially when you've got devs trying to test your changes out on their machines. permalink fedilink source parent hideshow 2 child comments replies: [–] Omgpwnies@lemmy.world 3 points 2 years ago (1 child) eh, just squash and merge. Feature branch can be messy as long as main is clean permalink fedilink source parent hideshow 2 child comments replies: [–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent [–] oce@jlai.lu 4 points 2 years ago* (1 child) Or just use a good IDE that makes doing atomic commits pretty natural. permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (2 children) I've only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I've never found it worth the trouble personally permalink fedilink source parent hideshow 4 child comments replies: [–] dukk@programming.dev 3 points 2 years ago (1 child) Shout out to Lazygit for letting me stage individual lines permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent [–] oce@jlai.lu 2 points 2 years ago You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It's much more convenient than commands and terminal text editors. permalink fedilink source parent
[–] Johanno@feddit.de 7 points 2 years ago (2 children) We make a singular commit per feature. permalink fedilink source parent hideshow 4 child comments replies: [–] KairuByte@lemmy.dbzer0.com 5 points 2 years ago I always find this hard to follow personally. permalink fedilink source parent [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (1 child) Trunk based, eh? Yeah, we do that on a couple teams where I'm at, too. I like the philosophy, but force pushing the same commit over and over as you're incorporating review feedback is antisocial, especially when you've got devs trying to test your changes out on their machines. permalink fedilink source parent hideshow 2 child comments replies: [–] Omgpwnies@lemmy.world 3 points 2 years ago (1 child) eh, just squash and merge. Feature branch can be messy as long as main is clean permalink fedilink source parent hideshow 2 child comments replies: [–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent
[–] KairuByte@lemmy.dbzer0.com 5 points 2 years ago I always find this hard to follow personally. permalink fedilink source parent
[–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (1 child) Trunk based, eh? Yeah, we do that on a couple teams where I'm at, too. I like the philosophy, but force pushing the same commit over and over as you're incorporating review feedback is antisocial, especially when you've got devs trying to test your changes out on their machines. permalink fedilink source parent hideshow 2 child comments replies: [–] Omgpwnies@lemmy.world 3 points 2 years ago (1 child) eh, just squash and merge. Feature branch can be messy as long as main is clean permalink fedilink source parent hideshow 2 child comments replies: [–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent
[–] Omgpwnies@lemmy.world 3 points 2 years ago (1 child) eh, just squash and merge. Feature branch can be messy as long as main is clean permalink fedilink source parent hideshow 2 child comments replies: [–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent
[–] Johanno@feddit.de 1 point 2 years ago Yep. You have to make sure your feature branch works. permalink fedilink source parent
[–] oce@jlai.lu 4 points 2 years ago* (1 child) Or just use a good IDE that makes doing atomic commits pretty natural. permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (2 children) I've only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I've never found it worth the trouble personally permalink fedilink source parent hideshow 4 child comments replies: [–] dukk@programming.dev 3 points 2 years ago (1 child) Shout out to Lazygit for letting me stage individual lines permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent [–] oce@jlai.lu 2 points 2 years ago You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It's much more convenient than commands and terminal text editors. permalink fedilink source parent
[–] pomodoro_longbreak@sh.itjust.works 2 points 2 years ago (2 children) I've only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I've never found it worth the trouble personally permalink fedilink source parent hideshow 4 child comments replies: [–] dukk@programming.dev 3 points 2 years ago (1 child) Shout out to Lazygit for letting me stage individual lines permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent [–] oce@jlai.lu 2 points 2 years ago You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It's much more convenient than commands and terminal text editors. permalink fedilink source parent
[–] dukk@programming.dev 3 points 2 years ago (1 child) Shout out to Lazygit for letting me stage individual lines permalink fedilink source parent hideshow 2 child comments replies: [–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent
[–] pomodoro_longbreak@sh.itjust.works 1 point 2 years ago Looks pretty neat. I like that it shows the commands it's issuing! permalink fedilink source parent
[–] oce@jlai.lu 2 points 2 years ago You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It's much more convenient than commands and terminal text editors. permalink fedilink source parent
[–] AnarchistArtificer@lemmy.world 3 points 2 years ago Yay, learning! permalink fedilink source parent
[–] dukk@programming.dev 7 points 2 years ago* (1 child) Better yet, git commit -p permalink fedilink source parent hideshow 2 child comments replies: [–] sip@programming.dev 6 points 2 years ago uuuuuuuu. and you could do -m to describe the commit. next they'll add --push/-P. perhaps add -r for fetch/rebase then commit. one command to rule them all! 😈 permalink fedilink source parent
[–] sip@programming.dev 6 points 2 years ago uuuuuuuu. and you could do -m to describe the commit. next they'll add --push/-P. perhaps add -r for fetch/rebase then commit. one command to rule them all! 😈 permalink fedilink source parent