potiuk commented on PR #54072: URL: https://github.com/apache/airflow/pull/54072#issuecomment-3148686588
> Should we have e2e testing separate repo and keep all the tests there and uses them part of workflow? 🤔 I think separate repo is generally a bad idea. Monorepo has it's drawbacks - but it has also benefits - for example much easier syncing of dependencie with workspace, keeping single contribuition workflow, being able to stop PR from merging when the tests fail etc. I can't see any real benefit of having separate repo for tests that **should** essentially be run as part of the same workflow as all other tests (especially when we have `uv sync` and workspaces. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
