I'm of the opinion that Git hooks are personal. That's why they're not part of the source code itself. I make extensive use of hooks, but they're tailored to my needs.
Note that you can skip hooks by passing the --no-verify flag to subcommands. Comes in handy when they're slow and you know that you've just fixed the wrong formatting that the previous invocation of your pre-commit hook complained about.
Nice, I use finicky as well, but now and again I have to change a rule or even add a new one. pisses me right off. Anyway thank you for sharing your dotfiles.
> Using commit log diffs as changelogs is a bad idea: they're full of noise. Things like merge commits, commits with obscure titles, documentation changes, etc.
> The purpose of a commit is to document a step in the evolution of the source code. Some projects clean up commits, some don't.
> The purpose of a changelog entry is to document the noteworthy difference, often across multiple commits, to communicate them clearly to end users.
> they're full of noise. Things like merge commits
From another angle, merge commits can also be a solution to the problem. `git merge --no-ff --edit` can be a great way to summarize an entire branch of commits. Most PR tools will give you an easy way to create those kind of merge commits. Don't settle for the default "merge branch x into y", create a meaningful title and fill in details/summary of what happened in the branch. With traversal tools like git log --first-parent you can see a high level of just your merge commits with the gnarly details of whatever steps led up to the merge commit itself.
I've certainly seen good projects where `git log --first-parent` was always a useful first pass changelog (no matter how "clean" the rest of commits were or were not). Probably still not a changelog you should send as a document to end users (because still written from a development standpoint rather than a user standpoint), but a good place to start writing the end user documentation.
Me too, but some tools combine the best of both worlds. In my team we use commitizen [1] which drinks both from keepachangelog and conventional commits and we are quite pleased with our changelogs so far.
> Facebook aside you really see this across the board on almost any platform, that once the product reaches it's 1.0 stage, (where it is good, does what the users want it to do, and has realised its vision) it begins a process of gradual decay, as the focus of the product managers (now panicking to find some statistics to improve to show their bosses) shifts from "building functionality" to "increasing engagement/retention/active users per month".
Best example for me: Revolut. The app and product as a whole was so simple and good.
One year ago (or maybe 1.5 years ago) it started going downhill, fast. The app got so complicated that I often simply cannot find what I'm looking for (my card or the balance in a specific currency). Everyone I know using Revolut has the same complaint, especially older people like my parents or in-laws.
Valora Digital | Senior iOS | Full-time | Zurich, Switzerland | ONSITE or REMOTE (CET +- 2h)
Valora Digital[0] is the digital unit of Valora[1], a European retailer with 2700 stores across 5 countries. We are tackling interesting challenges in areas such as Autonomous Stores (think Amazon Go), E-commerce & Delivery, Loyalty, Payments and Process Improvement. For this purpose we are building up a development team from scratch. You will be one of the first engineers and will have a big part in shaping the culture as well as choosing our stack. We are looking to bring the startup ethos to the corporate world and get to combine the best of both worlds: ample funding, a huge customer base to deploy to and lots of freedom.
We are using Swift and SwiftUI to build a modular architecture that will underpin a portfolio of apps. I'm head of mobile and an iOS developer myself.
Note that you can skip hooks by passing the --no-verify flag to subcommands. Comes in handy when they're slow and you know that you've just fixed the wrong formatting that the previous invocation of your pre-commit hook complained about.
reply