...

1. Clone the project

2. edit, git add, commit
   Write you change (remember to include `-s` to sign off commits: `git commit -s`)

3. git push

4. Click the link from the message to open a merge request to the repository

5. If you have multiple commits, write a detailed explanation about what you're asking to be merged in.
   Set the change to "Draft" if its still being worked on.

6. Wait for CI to pass and a CODEOWNER to review and merge.

Gitlab-CI

There is a lot of documentation available through Gitlab for building and maintaining .gitlab-ci.yml files.

...

The Releng project also maintains some of templates for projects to use; Projects are under no obligation or requirement to use the templates provided by the Releng project.
Help can always be requested through a  support ticket with the Linux Foundation release engineering team if projects need assistance configuring or debugging their CI jobs or pipelines.
These examples can be used to include the templates in your own project's .gitlab-ci.yml

---
include:
  - project: anuket/releng
    file: '/gitlab-templates/Docker.gitlab-ci.yml'

...

myscheduledjob:
  rules:
    - if: $CI_PIPELINE_SOURCE == "schedule" && $MY_SCHEDULE == "true"

...

When: Never

When specifying using if rules for a job, there is an implicit "- when: never" rule as the last in the list, unless a previous rule specified "never", a job will never be added if the only rules listed run "when: never" - There must always be a statement that specifies when the job is to be included in the pipeline in order for the job to run.

Hosted Runners (External Hardware builds)

...