style: format project

Author: PierreJeanjacquot

.github/workflows/docker-build-cloud.yml

@@ -28,7 +28,8 @@ on:
         default: "."
         type: string
       build-args:
-        description: "Docker build arguments (multiline format: KEY1=value1\nKEY2=value2)"
+        description:
+          "Docker build arguments (multiline format: KEY1=value1\nKEY2=value2)"
         default: ""
         type: string
       attest:

.github/workflows/docker-build.yml

@@ -4,7 +4,8 @@ on:
   workflow_call:
     inputs:
       build-args:
-        description: "Docker build arguments (multiline format: KEY1=value1\nKEY2=value2)"
+        description:
+          "Docker build arguments (multiline format: KEY1=value1\nKEY2=value2)"
         default: ""
         type: string
       image-name:
@@ -149,8 +150,8 @@ jobs:
           context: ${{ inputs.context }}
           file: ${{ inputs.dockerfile }}
           platforms: ${{ inputs.platform }}
-          load: true   # Make the image available on runner
-          push: false  # Don't push yet, wait for security checks
+          load: true # Make the image available on runner
+          push: false # Don't push yet, wait for security checks
           tags: ${{ inputs.image-name }}:${{ inputs.image-tag }}
 
       - name: Run Trivy vulnerability scanner

.github/workflows/docker-promote.yml

@@ -214,8 +214,8 @@ jobs:
           image-ref: ${{ env.IMAGE }}@${{ steps.tested.outputs.digest }}
           format: table
           ignore-unfixed: true
-          vuln-type: 'os,library'
-          severity: 'CRITICAL,HIGH'
+          vuln-type: "os,library"
+          severity: "CRITICAL,HIGH"
           hide-progress: true
           exit-code: 1
           # same scanner version as the CI build, so a finding here means the

.github/workflows/propose-safe-multisig-tx.yml

@@ -1,45 +1,45 @@
-name: 'Propose Safe Multisig Transaction'
+name: "Propose Safe Multisig Transaction"
 on:
   workflow_call:
     inputs:
       safe-address:
-        description: 'Address of the Safe contract'
+        description: "Address of the Safe contract"
         required: true
         type: string
       transaction-to:
-        description: 'Target address of the transaction'
+        description: "Target address of the transaction"
         required: true
         type: string
       transaction-value:
-        description: 'Value to send in the transaction (in wei, default: 0)'
+        description: "Value to send in the transaction (in wei, default: 0)"
         required: false
-        default: '0'
+        default: "0"
         type: string
       transaction-data:
-        description: 'Transaction data/calldata'
+        description: "Transaction data/calldata"
         required: true
         type: string
       dry-run:
-        description: 'If true, validate and prepare the transaction without proposing it'
+        description: "If true, validate and prepare the transaction without proposing it"
         required: false
         default: false
         type: boolean
     secrets:
       rpc-url:
-        description: 'RPC URL for the blockchain network'
+        description: "RPC URL for the blockchain network"
         required: true
       safe-proposer-private-key:
-        description: 'Private key of the proposer wallet'
+        description: "Private key of the proposer wallet"
         required: true
       safe-api-key:
-        description: 'Safe API key for transaction service'
+        description: "Safe API key for transaction service"
         required: true
     outputs:
       tx-hash:
-        description: 'Hash of the Safe transaction'
+        description: "Hash of the Safe transaction"
         value: ${{ jobs.propose-transaction.outputs.tx-hash }}
       tx-details:
-        description: 'Created transaction details'
+        description: "Created transaction details"
         value: ${{ jobs.propose-transaction.outputs.tx-details }}
 
 jobs:
@@ -48,7 +48,7 @@ jobs:
     outputs:
       tx-hash: ${{ steps.safe-transaction.outputs.tx-hash }}
       tx-details: ${{ steps.safe-transaction.outputs.tx-details }}
-    
+
     steps:
       - name: Checkout repository
         uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
@@ -58,7 +58,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
-          node-version: '22'
+          node-version: "22"
 
       - name: Install dependencies
         run: npm ci

.github/workflows/rust-build.yml

@@ -4,19 +4,19 @@ on:
   workflow_call:
     inputs:
       rust-version:
-        description: 'Rust version to use'
-        default: 'stable'
+        description: "Rust version to use"
+        default: "stable"
         type: string
       working-directory:
-        description: 'The directory to run jobs from'
-        default: '.'
+        description: "The directory to run jobs from"
+        default: "."
         type: string
       enable-cache:
-        description: 'Enable caching of dependencies'
+        description: "Enable caching of dependencies"
         default: true
         type: boolean
       publish-crates-io:
-        description: 'Publish package to crates.io'
+        description: "Publish package to crates.io"
         default: false
         type: boolean
     secrets:
@@ -26,7 +26,7 @@ on:
 env:
   CARGO_TERM_COLOR: always
   CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
-  
+
 jobs:
   build_and_publish:
     runs-on: ubuntu-latest
@@ -80,7 +80,7 @@ jobs:
       - name: Check documentation
         working-directory: ${{ inputs.working-directory }}
         env:
-          RUSTDOCFLAGS: '-D warnings'
+          RUSTDOCFLAGS: "-D warnings"
         run: cargo doc --locked --no-deps --document-private-items
 
       - name: Validate package

.github/workflows/validate-release-please-config.yml

@@ -5,16 +5,16 @@ on:
     branches:
       - main
     paths:
-      - 'release-please-config.json'
-      - 'scripts/check-release-please-config.sh'
-      - '.github/workflows/validate-release-please-config.yml'
+      - "release-please-config.json"
+      - "scripts/check-release-please-config.sh"
+      - ".github/workflows/validate-release-please-config.yml"
   push:
     branches:
       - main
     paths:
-      - 'release-please-config.json'
-      - 'scripts/check-release-please-config.sh'
-      - '.github/workflows/validate-release-please-config.yml'
+      - "release-please-config.json"
+      - "scripts/check-release-please-config.sh"
+      - ".github/workflows/validate-release-please-config.yml"
 
 permissions:
   contents: read

.github/workflows/verify-workflow-sha256.yml

@@ -5,18 +5,18 @@ on:
     branches:
       - main
     paths:
-      - '.github/workflows/*.yml'
-      - 'release-please-config.json'
-      - 'scripts/compute-workflow-sha256.sh'
-      - '**/workflow-sha256'
+      - ".github/workflows/*.yml"
+      - "release-please-config.json"
+      - "scripts/compute-workflow-sha256.sh"
+      - "**/workflow-sha256"
   push:
     branches:
       - main
     paths:
-      - '.github/workflows/*.yml'
-      - 'release-please-config.json'
-      - 'scripts/compute-workflow-sha256.sh'
-      - '**/workflow-sha256'
+      - ".github/workflows/*.yml"
+      - "release-please-config.json"
+      - "scripts/compute-workflow-sha256.sh"
+      - "**/workflow-sha256"
 
 permissions:
   contents: read

conventional-commits/README.md

@@ -1,10 +1,13 @@
 # 📝 Conventional Commits Workflow
 
 ## 🔍 Overview
+
 This reusable GitHub Actions workflow validates that pull request titles follow the [Conventional Commits](https://www.conventionalcommits.org/) specification. Conventional Commits provide a standardized format for commit messages, making it easier to generate changelogs, automate versioning, and understand the purpose of changes at a glance. By enforcing this standard, your repository maintains a clean and meaningful history that benefits both developers and automated tools.
 
 ## 📚 What are Conventional Commits?
+
 Conventional Commits follow this structured format:
+
 ```
 <type>[optional scope]: <description>
 
@@ -14,6 +17,7 @@ Conventional Commits follow this structured format:
 ```
 
 ### 🏷️ Common Types Include:
+
 - `✨ feat`: A new feature that adds functionality to your codebase
 - `🐛 fix`: A bug fix that resolves an issue or problem
 - `📖 docs`: Documentation changes or improvements
@@ -25,6 +29,7 @@ Conventional Commits follow this structured format:
 - `🔒 security`: Fixing security vulnerabilities or enhancing security
 
 ## 🌟 Benefits
+
 - **📋 Automated Changelog Generation**: Works seamlessly with tools like release-please to create detailed, organized changelogs without manual effort
 - **🔢 Semantic Versioning Automation**: Helps determine version bumps based on commit types (major, minor, patch) following SemVer principles
 - **📊 Improved Repository History**: Makes your project history more readable, structured, and navigable for all team members
@@ -37,10 +42,11 @@ Conventional Commits follow this structured format:
 ### 🔐 Secrets
 
 | Name | Description | Required |
-|------|-------------|----------|
+| --- | --- | --- |
 | `GITHUB_TOKEN` | GitHub token for authentication and PR interactions | Yes |
 
 ### 🛡️ Permissions
+
 The workflow requires `pull-requests: read` permission to access PR information and validate titles effectively.
 
 ## 💻 Example Usage
@@ -63,13 +69,15 @@ jobs:
 ```
 
 ## 📋 Implementation Notes
+
 - 🔄 The workflow runs automatically when PRs are opened, edited, or reopened to ensure continuous validation
 - ✅ It validates the PR title against the Conventional Commits specification with comprehensive checks
 - 💬 If validation fails, the workflow writes detailed guidance on how to fix the title to the job summary
 - 🔗 This workflow is particularly useful when combined with the release-please workflow for a fully automated release process
 - 🚀 Helps maintain a high-quality repository that's ready for automated versioning and changelog generation
 
 ## 🛠️ Troubleshooting
+
 - If PR titles are consistently failing validation, consider providing team training on Conventional Commits
 - For complex projects, you may want to define custom scopes that align with your project's architecture
 - Remember that only the PR title needs to follow the convention, not every commit message (though that's also beneficial)

docker-build-cloud/README.md

@@ -12,28 +12,27 @@ This reusable GitHub Actions workflow builds and pushes a multi-platform Docker
 - 🚀 No QEMU emulation, no native ARM runners — DBC handles arch-specific builds
 - 📜 Generates & signs a keyless SLSA build provenance attestation (optional)
 
-> [!IMPORTANT]
-> Requires a Docker Build Cloud subscription and a builder configured in your DockerHub organization. The DockerHub PAT must have the **Build** scope to authenticate to the cloud endpoint.
-
-## ⚙️  Inputs
-
-| Name                     | Description                                                                       | Required | Default        |
-| ------------------------ | --------------------------------------------------------------------------------- | -------- | -------------- |
-| `attest`                 | Generate & sign a keyless SLSA build provenance attestation for the pushed image (requires caller permissions, see notes) | No | `false` |
-| `build-args`             | Docker build arguments (multiline format: `KEY1=value1\nKEY2=value2`)             | No       | `""`           |
-| `cloud-builder-endpoint` | Docker Build Cloud endpoint, format `<dbc-org>/<builder>`                         | Yes      | -              |
-| `context`                | Path to Docker Build Context                                                      | No       | `"."`          |
-| `dockerfile`             | Path to the Dockerfile (e.g. `'./Dockerfile'`, `'./docker/Dockerfile'`)           | No       | `"Dockerfile"` |
-| `image-name`             | Name of Docker Image, fully qualified (e.g. `iexechub/my-image`)                  | Yes      | -              |
-| `image-tag`              | Tag to apply to the built image (e.g. `1.0.0`, no v prefix)                       | Yes      | -              |
-| `platforms`              | Comma-separated build platforms (e.g. `linux/amd64,linux/arm64`)                  | Yes      | -              |
+> [!IMPORTANT] Requires a Docker Build Cloud subscription and a builder configured in your DockerHub organization. The DockerHub PAT must have the **Build** scope to authenticate to the cloud endpoint.
+
+## ⚙️ Inputs
+
+| Name | Description | Required | Default |
+| --- | --- | --- | --- |
+| `attest` | Generate & sign a keyless SLSA build provenance attestation for the pushed image (requires caller permissions, see notes) | No | `false` |
+| `build-args` | Docker build arguments (multiline format: `KEY1=value1\nKEY2=value2`) | No | `""` |
+| `cloud-builder-endpoint` | Docker Build Cloud endpoint, format `<dbc-org>/<builder>` | Yes | - |
+| `context` | Path to Docker Build Context | No | `"."` |
+| `dockerfile` | Path to the Dockerfile (e.g. `'./Dockerfile'`, `'./docker/Dockerfile'`) | No | `"Dockerfile"` |
+| `image-name` | Name of Docker Image, fully qualified (e.g. `iexechub/my-image`) | Yes | - |
+| `image-tag` | Tag to apply to the built image (e.g. `1.0.0`, no v prefix) | Yes | - |
+| `platforms` | Comma-separated build platforms (e.g. `linux/amd64,linux/arm64`) | Yes | - |
 
 ## 🔐 Secrets
 
-| Name                 | Description                                                                                | Required |
-| -------------------- | ------------------------------------------------------------------------------------------ | -------- |
-| `dockerhub-username` | Username for Docker Hub authentication                                                     | Yes      |
-| `dockerhub-password` | Personal Access Token for Docker Hub with the **Build** scope (needed for DBC endpoint)    | Yes      |
+| Name | Description | Required |
+| --- | --- | --- |
+| `dockerhub-username` | Username for Docker Hub authentication | Yes |
+| `dockerhub-password` | Personal Access Token for Docker Hub with the **Build** scope (needed for DBC endpoint) | Yes |
 
 ## 💻 Example Usage
 
@@ -43,7 +42,7 @@ name: Build and Push Release Image
 on:
   push:
     tags:
-      - 'v*.*.*'
+      - "v*.*.*"
 
 jobs:
   build-multiplatform:

docker-build-cloud/workflow-sha256

@@ -1 +1 @@
-f364b67e9d5c3795461d15b7bab21adddcd63490e097a15aa82678f80212bff4
+6e473c36fb9cf55f91ebdfaa863b7019b2b143f63b20b618ef53c2229023ab05