Atmosphere uses a few different Git repositories to host the code for the project. This document explains how to work with the different repositories, their purpose, and how to maintain them.
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:
In order to create a new fork of an OpenStack repository, we'll need to create a fork under the vexxhost organization. In this example, we'll assume that you're creating a fork of the Horizon project.
In order to fork the project, you'll start with the following command which assumes that you have the gh command line tool installed:
./hack/repos/openstack/fork horizon
Once you're done, you'll also need to update the FORKED_PROJECTS variable in the internal/pkg/image_repositories/build_workflow.go file to include the newly forked project.
The only time that it is necessary to apply patches to the forked repositories is when there is a fix that has not yet been merged upstream. In order to apply a patch, you can use the following command which includes the project name and the Gerrit patch number:
./hack/repos/openstack/patch horizon 874351
This command will take care of automatically cloning the project, downloading the patch, and applying it to the repository. Once the patch has been applied, it will push it in a new branch to the forked repository and create a pull request.
Note*
If the process fails because of a merge conflict, you'll need to resolve the conflict and then run the command again.