When submitting patches to xen-devel, add a link to a successful pipeline run.
Signed-off-by: Stefano Stabellini <stefano.stabell...@amd.com> diff --git a/docs/process/sending-patches.pandoc b/docs/process/sending-patches.pandoc index 1991932b68..6e1401ea22 100644 --- a/docs/process/sending-patches.pandoc +++ b/docs/process/sending-patches.pandoc @@ -314,3 +314,23 @@ A patch should always be sent **to** the xen-devel mailing list of all touched code areas should get a copy of the mail via **Cc**. In case some other recipients are known to be interested in the patch, they can be added via **Cc**, too. + +## Testing + +Xen Project uses a GitLab-based CI infrastructure. You can request to +have your GitLab account added to the Xen Project organization on GitLab +(https://gitlab.com/xen-project) by reaching out to THE REST maintainers +via xen-devel or Matrix. Once your account is added to the Xen Project +organization on GitLab, also a personal Xen repository will be created +for you under https://gitlab.com/xen-project/people/<your-username>/xen. +You will be able to trigger a GitLab testing pipeline with a single git +push to your personal Xen repository. + +When submitting a non-trivial patch or a non-trivial patch series, +please include a link to the successful GitLab pipeline run on your +personal branch. This information can be added after the `---` line. +For example: + + --- + Test CI pipeline: + https://gitlab.com/xen-project/people/your-username/xen/-/pipelines/1980129839
