docs: add info about cherry-picking
diff --git a/docs/developer/repos.md b/docs/developer/repos.md
index d35a504..512b9db 100644
--- a/docs/developer/repos.md
+++ b/docs/developer/repos.md
@@ -45,11 +45,26 @@
> If the process fails because of a merge conflict, you'll need to resolve the
> conflict and then run the command again.
+## Cherry-picking patches
+
+If you need to cherry-pick a patch from one branch of a forked repository to
+another, you can use the following command:
+
+```bash
+./hack/repos/cherry-pick magnum fbfd3ce9a3 stable/zed
+```
+
+In the example above, this will cherry-pick the commit `fbfd3ce9a3` from the
+`master` branch of the `magnum` repository and create a pull request to apply
+it to the `stable/zed` branch.
+
## OpenStack
Atmosphere has a few forks of the OpenStack repositories. These are used to
apply patches to the upstream code that contain fixes which have not yet been
merged upstream. The list of forked repositories is as follows:
-* [openstack/cinder](https://github.com/vexxhost/cinder)
* [openstack/horizon](https://github.com/vexxhost/horizon)
+* [openstack/keystone](https://github.com/vexxhost/keystone)
+* [openstack/magnum](https://github.com/vexxhost/magnum)
+* [openstack/magnum-ui](https://github.com/vexxhost/magnum-ui)
diff --git a/internal/pkg/image_repositories/build_workflow.go b/internal/pkg/image_repositories/build_workflow.go
index 8b63590..5972333 100644
--- a/internal/pkg/image_repositories/build_workflow.go
+++ b/internal/pkg/image_repositories/build_workflow.go
@@ -6,9 +6,10 @@
)
var FORKED_PROJECTS map[string]bool = map[string]bool{
- "horizon": true,
- "keystone": true,
- "magnum": true,
+ "horizon": true,
+ "keystone": true,
+ "magnum": true,
+ "magnum-ui": true,
}
var EXTRAS map[string]string = map[string]string{}
var PROFILES map[string]string = map[string]string{