Skip to content

Add help commands to documentation #1075

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

Open
betulependule wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add help commands to documentation #1075

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 @@ -9,6 +9,11 @@ to trigger the Packit job manually.

![Re-run GitHub check](img/retriggering/comment.png)

### help
Packit is able to provide a help message summarizing all available commands and options:

/packit help

### 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
6 changes: 6 additions & 0 deletions fedora-ci/retriggering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,12 @@ sidebar_position: 2

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

## Help

Packit is able to provide a help message summarizing all available commands and options:

/packit-ci help

## Scratch builds

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