Skip to content

Document the support of command subarguments in the help handler #1173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
centosinfra-prod-github-app merged 1 commit into from
Sep 22, 2026
+10 −0
Merged

Document the support of command subarguments in the help handler #1173

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/retriggering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
5 changes: 5 additions & 0 deletions fedora-ci/retriggering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading