From 075f7e4a352e9ae69c7f3157907c18830933b4a8 Mon Sep 17 00:00:00 2001 From: Alzbeta Kucerova Date: Wed, 26 Nov 2025 14:11:16 +0100 Subject: [PATCH] Add documentation regarding the `--package` argument --- docs/retriggering.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/retriggering.md b/docs/retriggering.md index 0b6d9962aa..02bbce952e 100644 --- a/docs/retriggering.md +++ b/docs/retriggering.md @@ -9,6 +9,12 @@ to trigger the Packit job manually. ![Re-run GitHub check](img/retriggering/comment.png) +In case your project is a monorepository containing multiple packages, it is possible to specify which package to run jobs for. Use the `--package` argument for this purpose. Using this argument is useful for saving resources when you don't need to retrigger jobs for all packages. Use it as follows: + + /packit --package + +Do not use the `--package` argument in a project that is not a monorepository. + ### copr_build For retriggering the [`copr_build`](/docs/configuration/upstream/copr_build) jobs, Packit is able to trigger new builds based on a pull request comment: