Hi,
On Mon, Jul 24, 2023 at 9:47 AM Claus Ibsen wrote:
> Hi
>
> Ad 1)
> For basic stuff like a polish or update in a readme / doc file then direct
> push can be okay.
>
> However the GA action has improved a lot in recent time, so the time it
> takes for it to complete and the feedback it gives
Hi Andrea,
Thanks! After we get a consensus, I'll make sure we document that on the
contributor guidelines, so we have something to refer to and everyone knows
the expectations.
Kind regards
On Wed, Jul 19, 2023 at 10:47 AM Andrea Cosentino wrote:
> Hello Otavio,
>
> I'm answering inline.
>
>
Hi
Ad 1)
For basic stuff like a polish or update in a readme / doc file then direct
push can be okay.
However the GA action has improved a lot in recent time, so the time it
takes for it to complete and the feedback it gives now is more trustworthy.
Ad 2)
Yes this is good practice to squash - on
Hi,
+1 with this proposal, thx Otavio
Regards,
Nicolas
From: Otavio Rodolfo Piske
Sent: Wednesday, July 19, 2023 10:38
To: dev
Subject: Proposal for improving the way we collaborate on code improvements
Hi folks,
I am writing this proposed changes based on
Hello Otavio,
I'm answering inline.
Il giorno mer 19 lug 2023 alle ore 10:38 Otavio Rodolfo Piske <
angusyo...@gmail.com> ha scritto:
> Hi folks,
>
> I am writing this proposed changes based on the feedback received on the
> previous email where I shared some thoughts/concerns about improving ou
Hi folks,
I am writing this proposed changes based on the feedback received on the
previous email where I shared some thoughts/concerns about improving our
contribution practices (see the email entitled "Some thoughts on bisecting
Camel and our git commit practices" for details).
This is mostly a
