Thanks all for your responses.
> Perhaps instead of a checkbox we could auto-add a label that indicates
which API is being touched, based on which subfolder of api_fastapi. This
might be a better way to help meet your aim of helping with tracking down
changes, that isn't reliant on humans checkin
> based on what has changed. I need to take a look at how this can be done.
This should be very easy with boring-cyborg. What we **really** need to
make sure though is that our code is structured in the way that when we
select "paths" it nicely identifies the "impact". And rather than trying to
fi
One small thing though.. Currently boring cyborg usefulness is limited
because we have to manually "approve the workflows" that boring cyborg
runs. So might be a good opportunity to look how we can fix it, the problem
is that the boring cyborg is seen as a user who never committed anything to
our r
+1 (binding) - checked reproducibility, checksums, signatures, licences,
checked all my changes. Installed all providers except FAB on 2.10.5 and
they look good.
On Sat, Feb 22, 2025 at 2:45 PM Amogh Desai
wrote:
> +1 non binding
>
> The ones with testing impact:
> - https://github.com/apache/ai
