Add blog post for week 33

.pre-commit-config.yaml

@@ -7,7 +7,7 @@ repos:
     rev: v4.0.0-alpha.8
     hooks:
       - id: prettier
-        exclude: archetypes|docs|data|layouts|resources|source-git|static|themes/
+        exclude: archetypes|docs|data|layouts|resources|source-git|static|themes/|posts/aws-and-image-builder/index.md
   - repo: https://github.com/pre-commit/pre-commit-hooks
     rev: v5.0.0
     hooks:
@@ -20,3 +20,6 @@ repos:
         args:
           - https://github.com/packit/packit.dev.git
         stages: [manual, pre-push]
+
+ci:
+  autofix_prs: false

posts/aws-and-image-builder/index.md

@@ -49,7 +49,6 @@ automated solution. Below you can find a summary of all the needed manual steps;
 I am quite sure after reading them, you will want to automate them with Packit!
 
 - Build an RPM package with your pull request changes through **COPR**, go to https://copr.fedorainfracloud.org
-
   1. Install `copr-cli`.
   2. Create your account and service token.
   3. Add your token to `~/.config/copr.
@@ -58,14 +57,12 @@ I am quite sure after reading them, you will want to automate them with Packit!
   6. **WAIT for the build to finish**.
 
 - Create a new cloud image through the **Image Builder console**, go to https://console.redhat.com/insights/image-builder
-
   7. Login with your _Red Hat developer_ account.
   8. Click on the `Create Image` button, choose _AWS image_ type and follow the wizard.
   9. **WAIT for the build to finish**.
   10. Open the `Launch` link for the builded image.
 
 - Launch and access the AWS image through the **AWS management console**, go to https://aws.amazon.com/console/
-
   11. The previous link will open an AWS console tab with the
       _Launch an Instance_ wizard preset to use the builded image.
       You need to login into the _AWS management console_ using an _AWS Account ID_

src/pages/flock-2025-workshop.md

@@ -36,15 +36,13 @@ in general in the `rawhide` branch, but for experimentation during the workshop
 Then, the simplest ways of creating the config:
 
 - Use `packit dist-git init` (requires `packit` installed locally, e.g., `dnf install packit`)
-
   1.  In your cloned dist-git repository, switch to the target branch.
   2.  Run the command:
       ```bash
       packit dist-git init
       ```
 
 - Use our template
-
   1.  Manually create a `.packit.yaml` file in your target branch.
   2.  Copy the content from the [Downstream configuration template](https://packit.dev/docs/configuration/downstream_configuration_template#template) and adjust it to your needs.
 

weekly/2025/week-33.md

@@ -0,0 +1,15 @@
+---
+title: Week 33 in Packit
+date: 2025-08-18
+authors: nforro
+tags:
+  - 2025-August
+  - 2025
+  - August
+---
+
+## Week 33 (August 12th – August 18th)
+
+- In test jobs, it is now explicitly required to include the targets needed for running build jobs;
+  they will no longer be automatically deduced to prevent inconsistencies in creating build and test jobs.
+  ([packit-service#2785](https://github.com/packit/packit-service/pull/2785))