After seeing a few Conventional Commits messages, I personally do not find
them very useful.
Granted, the intention of clearly describing the change is good. However,
the "feat(abc)" prefixes do not add much value IMHO, but require extra
cognitive effort to parse. I still have to read the whole me
+1
And I think Alex is right: it could be helpful to update contributing file
in the repo and on the website.
Regards
JB
Le lun. 19 mai 2025 à 20:26, Alex Dutra a
écrit :
> Hi all,
>
> I'm obviously +1 on Robert's proposals. Should we modify our
> CONTRIBUTING.md guidelines?
>
> Also, in the s
TBH, I'm not up-to-date on Conventional Commits features, but if it is
possible
to flag and auto-extract breaking changes / use notes / etc. from commi
messages, it might be worth considering it as an alternative to my
CHANGELOG [1] proposal.
[1] https://lists.apache.org/thread/qznf8toht1r7ml35lt4
Hi all,
I'm obviously +1 on Robert's proposals. Should we modify our
CONTRIBUTING.md guidelines?
Also, in the spirit of standardizing how commit messages should be
formatted, I suggest that we take a look at the Conventional Commits
spec [1].
This small spec is becoming more and more popular (I
Hi all,
Looking a bit ahead with respect to releases and (semi) automatic releases:
We have a script that automatically collects the code changes from the
Git log and adds it to the release-notes. While PRs usually have some
meaningful information in the description, that information is often
+1 on this suggestion, it would be good practice for everyone.
Bests,
William
On Mon, May 19, 2025 at 7:56 AM Prashant Singh
wrote:
> +1 to the suggestion !
>
> On Mon, May 19, 2025 at 7:39 AM Dmitri Bourlatchkov
> wrote:
>
> > Great suggestions, Robert! Thanks for writing them down.
> >
> > C
+1 to the suggestion !
On Mon, May 19, 2025 at 7:39 AM Dmitri Bourlatchkov
wrote:
> Great suggestions, Robert! Thanks for writing them down.
>
> Cheers,
> Dmitri.
>
> On Mon, May 19, 2025 at 8:34 AM Robert Stupp wrote:
>
> > Hi all,
> >
> > Looking a bit ahead with respect to releases and (semi
Great suggestions, Robert! Thanks for writing them down.
Cheers,
Dmitri.
On Mon, May 19, 2025 at 8:34 AM Robert Stupp wrote:
> Hi all,
>
> Looking a bit ahead with respect to releases and (semi) automatic releases:
>
> We have a script that automatically collects the code changes from the
> Git
