From 9a70d37377f59f24f6d2938746f3a9217a39ce79 Mon Sep 17 00:00:00 2001 From: Alzbeta Kucerova Date: Wed, 16 Sep 2026 11:57:32 +0200 Subject: [PATCH] Document the support of command subarguments in the help handler --- docs/retriggering.md | 5 +++++ fedora-ci/retriggering.md | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/docs/retriggering.md b/docs/retriggering.md index d505f1763d..eb60ac4d73 100644 --- a/docs/retriggering.md +++ b/docs/retriggering.md @@ -20,6 +20,11 @@ Packit is able to provide a help message summarizing all available commands and /packit help +It is also possible to query the usage of a particular command. For example: + + /packit help test + /packit help pull-from-upstream + ### 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: diff --git a/fedora-ci/retriggering.md b/fedora-ci/retriggering.md index dcef165cfe..f3f5b3bcf2 100644 --- a/fedora-ci/retriggering.md +++ b/fedora-ci/retriggering.md @@ -20,6 +20,11 @@ Packit is able to provide a help message summarizing all available commands and /packit-ci help +It is also possible to query the usage of a particular command. For example: + + /packit-ci help scratch-build + /packit-ci help test + ## Restarting all CI jobs To restart the entire CI pipeline from the beginning, retrigger the [scratch build](#scratch-builds) — tests will automatically follow once it succeeds. There is no need to separately retrigger the tests.