Skip to content
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.

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

Docs for retriggering through issue comment #567

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 7 additions & 0 deletions content/docs/Configuration/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -336,6 +336,13 @@ By default, no issue will be created so Packit doesn't unintentionally spam any
By enabling this setting, Packit will either create a new issue or add a comment to an already existing issue.
In that case, the issue will be reused and a new comment will be added.

When a downstream job (e.g. Koji build or Bodhi update) fails,
you can re-trigger the failed job through a comment like
`/packit koji-build` or `/packit create-update` in the opened issue.
The Packit app has to be installed in the issue repository and the
user, who commented, needs to have write permissions
into the repository in order for the retriggering to work.

#### copy_upstream_release_description

(*bool*) When doing a new update in Fedora dist-git, the [GitHub upstream release description](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases)
Expand Down
7 changes: 7 additions & 0 deletions content/docs/guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -298,6 +298,13 @@ or are run in a particular step as a hook (with no action run by default).
Take a look at the tables [here](/docs/actions/) to know what actions are available for each job.


### Users

Packit checks if the user has sufficient permissions to complete a job (this depends on the job type).
For this reason the profile of a Packit user has to be accessible.
For example, on Github this means that the membership of a user to their team has to be public (see https://github.com/orgs/[org_name]/people/[user_name] ).


### How to try that for real

In order to start using Packit, we suggest you [install the tooling locally](/docs/cli/#installation). All
Expand Down