Aidan Casey

@Treggats - Can you also rebase?

@Treggats - I'm not a huge fan of the fact that Rector isn't showing us what it would change. Let's update the action to include that.

@Treggats they originally started as a single job, but as we considered things we might be looking to add in the future (automatic comments to PRs, etc.) it felt cleaner...

@Treggats does Rector have a CI mode like CS fixer? One of the decisions we made there was that those CI tools would not automatically write back to the repo...

> On the subject of splitting of, if we need to have recurring action/jobs/etc. it's possible to create our own custum action and reference that. Sure, but now you're still...

Here is a diagram of how we will try and set this up. The goal will be to eliminate the chicken and egg problem with the bootstrappers where they are...

Hands down agree, @innocenzi. Long term, I'd really love to see Tempest play nicely with microservices/other languages in the queue as well. This is something that I firmly believe PHP...

@shaffe-fr I'm _thinking_ we should separate out local filesystem and third-party storage as two different packages in Tempest world, with priority on the former. For example: ```php // Local filesystem...

You have quite the list of potential changes here. At the end of the day, _why_ should we change the current implementation to utilize bootstrappers/bootloaders?

To be completely fair, I'm not saying it's a bad idea. A lot of frameworks take this approach differentiating between "bootstrappers" which setup the application and "service providers" which act...