You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a LOT of repo infra / config that can easily get out of date:
GitHub action scripts
TypeScript config
Automated testing config
(hopefully) PHPStan config
Because of Flarum's many-extension architecture, there are also a LOT of repos to keep track of / keep up to date. This is tedious and not scalable.
I believe we should use flarum-cli as the single source of truth for all this repo infrastructure. We can store the "proper" config via the boilerplate extension, and the infra commands that automatically update parts of extension skeletons. Then, a flarum audit infra command can be used to check whether any infra is out of date / not in compliance with our opinionated specs.
Furthermore, we can add a GItHub action to every Flarum repo that runs flarum-cli infra audit to see whether anything is out of date. This will make it really easy to keep Flarum repo infra up to date.
The text was updated successfully, but these errors were encountered:
The other option would be to make all of the GitHub actions infrastructure Github Action packages, (I think you can do that) thus updating one package updates everything across our entire organization, similar to the way that our JS build action works.
The other option would be to make all of the GitHub actions infrastructure Github Action packages, (I think you can do that) thus updating one package updates everything across our entire organization, similar to the way that our JS build action works.
We'd still need to bump versions across all repos, plus that doesn't help with typescript config, testing, etc.
Feature Request
There is a LOT of repo infra / config that can easily get out of date:
Because of Flarum's many-extension architecture, there are also a LOT of repos to keep track of / keep up to date. This is tedious and not scalable.
I believe we should use
flarum-cli
as the single source of truth for all this repo infrastructure. We can store the "proper" config via the boilerplate extension, and theinfra
commands that automatically update parts of extension skeletons. Then, aflarum audit infra
command can be used to check whether any infra is out of date / not in compliance with our opinionated specs.Furthermore, we can add a GItHub action to every Flarum repo that runs
flarum-cli infra audit
to see whether anything is out of date. This will make it really easy to keep Flarum repo infra up to date.The text was updated successfully, but these errors were encountered: