This automates the process, for all 20 macOS apps, that got framed up in #26080, with an ee/maintained-apps/inputs dir containing enough information to build the outputs via code that should also live in ee/maintained-apps. See this comment for more info.
When complete, when running the GitHub Action, we should be able to get automated PRs for any changes in Homebrew for all 20 existing FMAs we have, with a no-op if nothing changed (including where to download the current version).
We'll do this by extracting the existing script generation etc. code from our codebase and moving it to run via the GitHub Action. We can include in the inputs files instructions like we have inside apps.json, e.g. pre_uninstall_scripts. Inputs file format is deliberately left unspec'd to allow for the most reasonable division of config between the new equivalent of ingest.go and the JSON, since we'll be shipping those changes in lockstep (which means we don't need to maintain forward/backward compatibility at that layer).
Part of scope is adding contributor docs to ee/maintained-apps that are detailed enough that @harrisonravazzolo can dogfood this by adding Logi.
This automates the process, for all 20 macOS apps, that got framed up in #26080, with an
ee/maintained-apps/inputsdir containing enough information to build the outputs via code that should also live inee/maintained-apps. See this comment for more info.When complete, when running the GitHub Action, we should be able to get automated PRs for any changes in Homebrew for all 20 existing FMAs we have, with a no-op if nothing changed (including where to download the current version).
We'll do this by extracting the existing script generation etc. code from our codebase and moving it to run via the GitHub Action. We can include in the inputs files instructions like we have inside
apps.json, e.g.pre_uninstall_scripts. Inputs file format is deliberately left unspec'd to allow for the most reasonable division of config between the new equivalent ofingest.goand the JSON, since we'll be shipping those changes in lockstep (which means we don't need to maintain forward/backward compatibility at that layer).Part of scope is adding contributor docs to
ee/maintained-appsthat are detailed enough that @harrisonravazzolo can dogfood this by adding Logi.