In the preparing patches section, note that it is possible to run CI
tests via gitlab prior to submitting patches.

Signed-off-by: Tim Small <t...@seoss.co.uk>
---
 docs/hacking.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/hacking.rst b/docs/hacking.rst
index 85918c9176..c2e79e4501 100644
--- a/docs/hacking.rst
+++ b/docs/hacking.rst
@@ -58,6 +58,14 @@ adding a new feature or changing the output of a program, and
 don't forget to update the `release notes <news.html>`__ if your
 changes are significant and user-visible.
 
+To test across a variety of build platforms prior to submitting
+your changes, you may create your own fork of the project on
+gitlab. This will give you access to (a subset of) libvirt's
+`continuous integration <ci.html>`__ test suite.
+
+Please note that you should still follow the instructions below,
+rather than following gitlab's prompts to open a "merge request".
+
 Submitting patches
 ==================
 
-- 
2.39.2

Reply via email to