Creating merge requests
| 🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions. |
After deploying the registry regulations, only one version of changes is available — the master version.
Users have the ability to create a new merge request. This operation will create a new merge request based on the current master version of the regulations. Each request creates a new branch, which represents a candidate version, for making changes to the regulations.
| Making any changes to the regulations in the master version is not possible. It is necessary to create a new merge request to work with the regulations. |
| Any new version of changes is always created based on the latest changes in the master version. So, even if you are on a candidate version and want to create a new merge request, the new candidate version will still be created based on the master version. |
1. Creating a request
To create a merge request, follow these steps:
-
Expand the drop-down menu for version control in the top left corner of the page.
-
Select Create new request.
-
In the new window, fill in the required fields:
-
In the Version name field, enter the name of the change. This will be the name of your candidate version. For example,
candidate-version-01.Length: 3-32 characters. Allowed characters are “a-z”, “а-я”, 0-9, “-”.
-
In the Change description field, briefly describe the proposed changes for this candidate version. For example,
Test changes to the registry regulations.Length up to 512 characters. All characters are allowed except
""(double quotes), use''(single quotes) instead.If the Change description field contains double quotes (" "), you will not be able to create the merge request due to validation. The same logic applies to the validation rules described in the tooltip for each field. In this case, you will see an error prompt on the interface: "Check the format of the field":
-
-
Click
Create.
As a result, a new candidate version will be created. The user will automatically switch to the newly created version.
After creating a new candidate version, you can view its status and settings.