Skip to content

Add documentation regarding the --package argument #1073

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 documentation regarding the --package argument #1073

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
6 changes: 6 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,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 <job-you-want-to-trigger> --package <package-to-run-jobs-for>

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:

Expand Down