Deploy from GitHub: environments follow a branch
An app's environment can now follow a GitHub branch from Settings → Git. A push to the branch syncs the environment's files, as ib-apps push would, and production deploys from a development environment that takes the push, so a merge to main ships with no CI workflow or API key.
It uses the GitHub App Auditor uses, so a repository it already reviews is ready to pick. A folder inside the repository serves a monorepo, and .ibignore applies as with the CLI. Each sync is a GitHub Deployment on the commit, successful with the environment's address or failed with a link to its Logs, and Settings → Deploys shows which commit production runs.
A followed environment changes only through its branch: the file editor, the assistant and ib-apps push are refused with the branch named, and production's Deploy button gives way to the push. A deleted branch or a removed repository stops the following and leaves the files as they are.
More in Deploying from GitHub.