Ouro Current
Ouro UI releases, delivered as one pull request that merges on green.
Install the Ouro Current GitHub App on a repository. When Ouro UI, Ouro UI core or Ouro UI for Apple releases, that repository gets one pull request, “Update to Ouro UI vX”, with auto-merge on. Your own checks decide whether it lands.
Nothing to set up: it finds the pin files by their names. To stop it, uninstall the app from the repository’s settings.
What it does
It finds your pins
It reads the Ouro HX install record, files vendored from Ouro UI core or from a commit, SwiftPM, XcodeGen, an Xcode project and a workflow's OURO_UI_TAG.
It moves them to the latest release
An Ouro HX file takes the new release's source, written to your aliases the way the shadcn CLI writes it, and files the release added come with it.
It keeps one pull request
One branch, ouro-current/update, and one pull request per repository, updated in place when a newer release comes. Auto-merge is on, squash where the repository allows it, else a merge commit.
What it leaves alone
- It never writes to your default branch and never merges anything itself.
- It never overwrites a file you edited; it names that file in the pull request instead.
- It never names a private repository in public, here or in its run's log.
Who it keeps current
Checked , in 0 installations: 0 public repositories with Ouro UI pins, 0 with an update open. current.json.
Ouro Current lists a public repository here once it is installed on one. Install it on yours, and it is listed after the next run.