Skip to content

Commit 8561e82

Browse files
committed
Add help commands to documentation
Add information regarding the `/packit help` and `/packit-ci help` commands, which can be used in comments in PRs, to the documentation.
1 parent 0c6b8a7 commit 8561e82

2 files changed

Lines changed: 11 additions & 0 deletions

File tree

docs/retriggering.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,11 @@ In case your project is a monorepository containing multiple packages, it is pos
1515

1616
Do not use the `--package` argument in a project that is not a monorepository as that will result in no jobs being triggered. Also make sure not to switch the order of arguments as the `--package` argument has to be specified first in order to work.
1717

18+
### help
19+
Packit is able to provide a help message summarizing all available commands and options:
20+
21+
/packit help
22+
1823
### copr_build
1924
For retriggering the [`copr_build`](/docs/configuration/upstream/copr_build) jobs, Packit is able to trigger new builds based on a pull request comment:
2025

fedora-ci/retriggering.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,12 @@ sidebar_position: 2
55

66
You can retrigger CI jobs in dist-git pull requests by posting comments that include the appropriate `/packit-ci` commands, as outlined below.
77

8+
## Help
9+
10+
Packit is able to provide a help message summarizing all available commands and options:
11+
12+
/packit-ci help
13+
814
## Scratch builds
915

1016
To retrigger a scratch build, add the following comment to the pull request:

0 commit comments

Comments
 (0)