component-guide: add tip for running CI pipeline manually

When first importing a package, the `Run pipeline` button doesn't appear
in Gitlab's UI and a workaround is needed to trigger the first pipeline.
This commit adds a tip for such situations.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

content/guides/component_guide.md

@@ -122,8 +122,8 @@ This is the process to import a new package from Debian to Apertis:
   {{% /notice %}}
 
 * As the CI configuration was set by `gitlab-rulez` after the initial commit,
-  it will be necessary to run the CI/CD pipeline on each `apertis/*` branch to
-  push the package through to OBS.
+  it will be necessary to [run the CI/CD pipeline](#updating-components-from-debian)
+  on each `apertis/*` branch to push the package through to OBS.
 
   {{% notice warning %}}
   Ensure that one branch successfully completes it's upload to OBS before
@@ -251,6 +251,12 @@ To trigger the updates pipeline:
 - Navigate to the "Pipelines" page of the component in GitLab.
 - Click on the `Run pipeline` button in the top right-hand corner.
 ![Run Pipeline button](/images/run-pipeline-button.png)
+
+{{% notice tip %}}
+If the `Run pipeline` button doesn't appear, append `/new` to the page URL, for
+example `https://gitlab.apertis.org/pkg/hello/-/pipelines/new`.
+{{% /notice %}}
+
 - Select the relevant `debian/*` branch that you would like to update (such as
   `debian/bullseye`) under `Run for branch name or tag` and click the `Run
   pipeline` button shown on that page.