Re:Git: Using Advanced Rebase Features for a Clean Repository
by maxxxxx on Wednesday August 09, 2017 @10:55AM
(#14969620)
Do people actually look at the history a lot? After a pull request has been merged I rarely look at the history and I am really not interested in it. This is for a small team with around 5 people. In larger teams is it more important to see the history?
[ Parent
| on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository
by branja on Wednesday August 09, 2017 @12:23PM
(#14970857)
I work as lead dev on a 5 year old web app I took over from a previous dev and his team of subcontractors about a year ago. It's very helpful to see into the past when there's no way to just ask the previous dev.
Re:Git: Using Advanced Rebase Features for a Clean Repository
by Vinnl on Thursday August 10, 2017 @01:26AM
(#14976701)
Even if not at the history directly, commit messages are associated with the lines they edit. This provides great granular documentation: https://vincenttunru.com/assets/img/Commits-are-documentatio...
(From my blog post about why history matters: https://vincenttunru.com/Spend-effort-on-your-Git-commits/ )
Re:Git: Using Advanced Rebase Features for a Clean Repository
by james-skemp on Wednesday August 09, 2017 @02:47PM
(#14972369)
I work in a University setting where we have student's working in our various projects. While some stay with us for a number of years, some are with us for a semester or two.
Even with full-time staff, in the almost 6 years I've been here the rest of the dev and design staff completely changed (and grew).
In my opinion, if you're not using history/blame your code is relatively new, or you're the only one touching code. Or you have regular code reviews (paired programming, whatever).
Seven years at my last job was just full-time staff, but we had the same issues, once a version control system was actually implemented.