You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Shahar Epstein <sh...@apache.org> on 2026/06/16 22:02:07 UTC
[LAZY-CONSENSUS] Usage of imperative mode in commits
Hey,
Following the discussion in this thread
<https://lists.apache.org/thread/g34gx1tv8slorfy9hw7ks8wkkk86nxq0> (as well
as a complimentary discussion
<https://apache-airflow.slack.com/archives/C06K9Q5G2UA/p1781615008146859>
on Slack),
I'd like to call for a lazy-consensus on usage of imperative mode in
commits, by adding the following rule to the contributing docs in the PR
section (introduced by PR #68631
<https://github.com/apache/airflow/pull/68631>):
```
In text descriptions - always use imperative mode, never use past
tense or conventional commits or any prefixes in the title take precious
space and do not add any value, so they should be
avoided. For example, instead of "feat: add new feature" or "Added this
new feature"
use "Add new feature". This is a common convention in many open source
projects
and it makes the commit history more readable and consistent.
```
The lazy consensus will be reached in 72 hours on: June 20, 2026, 10:00 PM
UTC.
No need to reply unless you object to the proposal.
Shahar
Re: [LAZY-CONSENSUS] Usage of imperative mode in commits
Posted by Shahar Epstein <sh...@apache.org>.
Consensus reached.
Shahar
On Wed, Jun 17, 2026 at 1:02 AM Shahar Epstein <sh...@apache.org> wrote:
> Hey,
>
> Following the discussion in this thread
> <https://lists.apache.org/thread/g34gx1tv8slorfy9hw7ks8wkkk86nxq0> (as
> well as a complimentary discussion
> <https://apache-airflow.slack.com/archives/C06K9Q5G2UA/p1781615008146859>
> on Slack),
> I'd like to call for a lazy-consensus on usage of imperative mode in
> commits, by adding the following rule to the contributing docs in the PR
> section (introduced by PR #68631
> <https://github.com/apache/airflow/pull/68631>):
>
> ```
> In text descriptions - always use imperative mode, never use past
> tense or conventional commits or any prefixes in the title take
> precious space and do not add any value, so they should be
> avoided. For example, instead of "feat: add new feature" or "Added this
> new feature"
> use "Add new feature". This is a common convention in many open source
> projects
> and it makes the commit history more readable and consistent.
> ```
>
> The lazy consensus will be reached in 72 hours on: June 20, 2026, 10:00
> PM UTC.
> No need to reply unless you object to the proposal.
>
>
> Shahar
>