alexisruccius
Why doesn’t Phoenix use Conventional Commit prefixes?
Hi everyone,
I noticed that the Phoenix framework doesn’t use Conventional Commit prefixes like feat:, fix:, or docs: in its commit messages.
Is there a reason this style isn’t common in Elixir projects? Would using it be helpful or unnecessary for open source libraries?
I’m deciding whether to adopt it in my own project—curious to hear your thoughts.
Thanks! ![]()
Most Liked
sorentwo
Personally I greatly dislike the “conventional commit” style and prefer descriptive, sentence case commits with additional context. I’ll rewrite the message for pull requests that start with “feat:” to match the style of the repository.
When it comes to the changelog, I group bugs and enhancements, but do it when I’m writing the changelog. The messages usually get expanded into something more descriptive as well.
chrismccord
The phoenix team is lucky to get a descriptive commit out of me. Gary is the MVP of commits in this regard. Conventional commit stuff seems fine, and I would have no issue following it on a team if mandated. Don’t overthink it ![]()
adamu
You could try unconventional commits. ![]()
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








