packit · softwarefactory-project-zuul · Aug 19, 2025 · Jul 30, 2025
diff --git a/docs/configuration/downstream/bodhi_update.md b/docs/configuration/downstream/bodhi_update.md
@@ -5,6 +5,8 @@ sidebar_position: 3
 
 # `job: bodhi_update`
 
+![Bodhi updates](../../img/configuration/bodhi-updates.png)
+
 Create a new update in
 [Fedora Bodhi](https://bodhi.fedoraproject.org) for successful
 Koji build.

diff --git a/docs/configuration/downstream/koji_build.md b/docs/configuration/downstream/koji_build.md
@@ -5,6 +5,8 @@ sidebar_position: 2
 
 # `job: koji_build`
 
+![Koji build](../../img/configuration/koji-info.png)
+
 Trigger the build in
 [Fedora Koji](https://koji.fedoraproject.org/koji/) build system
 as a reaction to a new dist-git commit.

diff --git a/docs/configuration/upstream/copr_build.md b/docs/configuration/upstream/copr_build.md
@@ -5,6 +5,8 @@ sidebar_position: 1
 
 # `job: copr_build`
 
+![Copr build](../../img/configuration/copr-overview.png)
+
 Create an SRPM and submit an RPM build to [Fedora Copr](https://copr.fedorainfracloud.org/) build system.
 
 

diff --git a/docs/fedora-releases-guide/index.md b/docs/fedora-releases-guide/index.md
@@ -11,13 +11,17 @@ Let's split the release process into single steps:
 4. [Koji builds](#koji-build-job)
 5. [Bodhi updates](#bodhi-update-job)
 
+![Release steps](../img/fedora-releases-guide/release-steps.png)
+
 Doing Fedora releases with Packit means utilising these jobs:
 1. [`propose_downstream` or `pull_from_upstream`](#propose-downstream-or-pull-from-upstream)
 2. [`koji_build`](#koji-build-job)
 3. [`bodhi_update`](#bodhi-update-job)
 
 Every job takes care of a different part of the release process.
 
+![Packit flow chart](../img/fedora-releases-guide/process-diagram.png)
+
 :::tip
 In this page, you can find all the details of the release process automation covered by Packit.
 
@@ -233,6 +237,8 @@ By default, only merged pull requests created by Packit are being acted upon, bu
 you can override this behaviour by specifying
 `allowed_pr_authors` and/or `allowed_committers` in the [job configuration](/docs/configuration/downstream/koji_build).
 
+![Koji build](../img/fedora-releases-guide/koji-build.png)
+
 For a configuration example and retriggering, see [dist-git onboarding](./dist-git-onboarding.md#koji-build-job).
 
 ## Bodhi update job
@@ -246,6 +252,8 @@ By default, only successful Koji builds created by Packit are being acted upon,
 you can override this behaviour by specifying
 `allowed_builders` in the [job configuration](/docs/configuration/downstream/bodhi_update).
 
+![Bodhi updates](../img/fedora-releases-guide/bodhi-updates.png)
+
 For a configuration example and retriggering, see [dist-git onboarding](./dist-git-onboarding.md#bodhi-update-job).
 
 

diff --git a/docs/fedora-releases-guide/non-divergent-dist-git-branches.md b/docs/fedora-releases-guide/non-divergent-dist-git-branches.md
@@ -5,6 +5,8 @@ sidebar_position: 7
 
 # Non-divergent dist-git branches
 
+![Branches](../img/fedora-releases-guide/non-divergent-branches.png)
+
 To prevent your dist-git branches from diverging, you can use the following `dist_git_branches` syntax:
 
 ```yaml

diff --git a/docs/img/configuration/bodhi-updates.png b/docs/img/configuration/bodhi-updates.png
diff --git a/docs/img/configuration/copr-overview.png b/docs/img/configuration/copr-overview.png
diff --git a/docs/img/configuration/koji-info.png b/docs/img/configuration/koji-info.png
diff --git a/docs/img/fedora-releases-guide/bodhi-updates.png b/docs/img/fedora-releases-guide/bodhi-updates.png
diff --git a/docs/img/fedora-releases-guide/koji-build.png b/docs/img/fedora-releases-guide/koji-build.png
diff --git a/docs/img/fedora-releases-guide/non-divergent-branches.png b/docs/img/fedora-releases-guide/non-divergent-branches.png
diff --git a/docs/img/fedora-releases-guide/process-diagram.png b/docs/img/fedora-releases-guide/process-diagram.png
diff --git a/docs/img/fedora-releases-guide/release-steps.png b/docs/img/fedora-releases-guide/release-steps.png
diff --git a/docs/img/retriggering/comment.png b/docs/img/retriggering/comment.png
diff --git a/docs/retriggering.md b/docs/retriggering.md
@@ -7,6 +7,8 @@ sidebar_position: 7
 In general, you can put a `/packit <job-you-want-to-trigger>` comment
 to trigger the Packit job manually.
 
+![Re-run GitHub check](img/retriggering/comment.png)
+
 ### 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:
Original file line number	Diff line number	Diff line change
Expand Up		@@ -5,6 +5,8 @@ sidebar_position: 1

		# `job: copr_build`

		![Copr build](../../img/configuration/copr-overview.png)

		Create an SRPM and submit an RPM build to [Fedora Copr](https://copr.fedorainfracloud.org/) build system.


Expand Down
-Original file line number
+Diff line change
@@ Expand Up / @@ -5,6 +5,8 @@ sidebar_position: 7 @@
     # Non-divergent dist-git branches
+    ![Branches](../img/fedora-releases-guide/non-divergent-branches.png)
     To prevent your dist-git branches from diverging, you can use the following `dist_git_branches` syntax:
     ```yaml
@@ Expand Down @@