Disable autofixes by pre-commit CI and satisfy prettier

Signed-off-by: Nikola Forró <nforro@redhat.com>

Author: nforro

.pre-commit-config.yaml

@@ -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,25 +57,23 @@ 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.
+  1. Login with your _Red Hat developer_ account.
+  2. Click on the `Create Image` button, choose _AWS image_ type and follow the wizard.
+  3. **WAIT for the build to finish**.
+  4. 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_
-      allowed to access the _AMI Image_ you just created.
-  12. Select a **Key pair**, or create one if you don't have it already,
-      to be able to ssh the image later.
-  13. Click on `Launch Instance`
-  14. Connect to instance using an ssh client
-  15. Add the previously created COPR repo to the list of available dnf repositories.
-  16. Install the package you have created at step number 4.
-  17. Now you are ready to test your code in a real cloud image.
+  1. 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_
+     allowed to access the _AMI Image_ you just created.
+  2. Select a **Key pair**, or create one if you don't have it already,
+     to be able to ssh the image later.
+  3. Click on `Launch Instance`
+  4. Connect to instance using an ssh client
+  5. Add the previously created COPR repo to the list of available dnf repositories.
+  6. Install the package you have created at step number 4.
+  7. Now you are ready to test your code in a real cloud image.
 
 For every new pull request you want to test directly in a cloud image you have to repeat
 steps 4-16 or automate them through Packit!

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.