diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 5a273e46f00fdb78bbd746446f6527955ece4979..f49bc7ee02ef29ba1de2dfc499c2d946e650421a 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -9,7 +9,7 @@ generate-child-pipeline:
       cat > child-pipeline.yml << EOF
       stages:
         - generate-operators
-        - file-mr
+        - submit-merge-request
 
       generate-operators:
         stage: generate-operators
@@ -44,8 +44,8 @@ generate-child-pipeline:
     - |
       cat >> child-pipeline.yml << EOF
 
-      file-mr:
-        stage: file-mr
+      submit-merge-request:
+        stage: submit-merge-request
         when: manual
         before_script:
           - apt-get update -yqq
diff --git a/README.md b/README.md
index 3be071ce85492cc55284e3acd6b61b32c02d1bec..5edec04275ff1585ed72df8a06d9a111d405f7f2 100644
--- a/README.md
+++ b/README.md
@@ -30,5 +30,5 @@ It is a good idea to test your changes locally.
 In your commit, do not include changes to the `operators` directory.
 After pushing your changes to the remote, our CI automatically regenerates all operators from all `operators-<operator-group>.toml` files present in the repository.
 In this process, any changes you made under `operators` will be lost.
-After the pipeline has passed, you can trigger the manual job `file-mr` to create a new merge request including your changes and the freshly generated operators.
+After the pipeline has passed, you can trigger the manual job `submit-merge-request` to create a new merge request including your changes and the freshly generated operators.
 Using the CI makes sure that the generated code is always in sync with the description of what and how to generate.