> That was a temporary issue - it is green now. I needed to figure out how
to
name checks properly, and it turned out that "Tests / Finalize tests /
Summarize Warnings" is named (for whatever reason) as "Finalize tests /
Summarize Warnings" when run as part of the composite "umbrella" workflow
"Tes
fab provider is excluded and will have rc2
On Fri, Apr 25, 2025 at 8:03 PM Aritra Basu
wrote:
> +1 (non binding)
> --
> Regards,
> Aritra Basu
>
> On Fri, 25 Apr 2025, 8:23 pm Buğra Öztürk,
> wrote:
>
> > +1 non-binding
> >
> > On Fri, 25 Apr 2025, 16:39 Vishnu Chilukoori, >
> > wrote:
> >
> >
I am not sure if I like this feature a lot with my recent experience with
this PR: https://github.com/apache/airflow/pull/49692.
On the PR status, it mentions "finalize tests" is waiting to report status
but when i describe the tests, I see that task has completed.
It is quite confusing to me wit
On Sat, Apr 26, 2025 at 3:02 PM Amogh Desai
wrote:
> I am not sure if I like this feature a lot with my recent experience with
> this PR: https://github.com/apache/airflow/pull/49692.
>
> On the PR status, it mentions "finalize tests" is waiting to report status
> but when i describe the tests, I
Hi all,
thanks for tuning on auto-merge.
Agree that there might be a residual risk that pipeline goes green "too
early" and approval is there... but I think we need to use carefully.
I just did my first auto merge and carefully watched... all looks good.
If it helps in only 50% of cases to r
Hello everyone,
With some initial teething problems we've enabled an "experimental" feature
of "auto-merging" PRs in our repo. It should potentially help with "focus"
of maintainers, because they will not have to come-back to the PRs to merge
it once they enabled auto-merge for them.
It works in
