docs: update README

Author: TartanLeGrand

README.md

@@ -1,17 +1,23 @@
-# iExec reusable workflow repository
+# 🔄 iExec Reusable Workflow Repository
 
-This repository contains a reusable workflow for iExec. It is a monorepo that contains the following components:
+📝 This repository contains reusable workflows for iExec. It is a monorepo that contains the following components:
 
-## Components
+## 📦 Components
 
-### [Build Docker Image](./docker-build)
+### 🐳 [Build Docker Image](./docker-build)
 This workflow builds a Docker image from a Dockerfile. It is a reusable workflow that can be used in other workflows.
 
-### [Release Please](./release-please)
+### 🚀 [Release Please](./release-please)
 This workflow uses the [release-please-action](https://github.com/googleapis/release-please-action) to automate the release of a project.
 
-### [Publish NPM Package](./publish-npm)
+### 📦 [Publish NPM Package](./publish-npm)
 This workflow publishes an NPM package to the NPM registry.
 
-### [Conventional Commits](./conventional-commits)
+### ✅ [Conventional Commits](./conventional-commits)
 This workflow checks that pull request titles follow the [Conventional Commits](https://www.conventionalcommits.org/) specification.
+
+### 🦀 [Rust Build](./rust-build)
+This workflow builds and tests Rust projects.
+
+### 🧹 [Stale](./stale)
+This workflow marks and closes stale issues and pull requests.

conventional-commits/README.md

@@ -1,14 +1,14 @@
-# Conventional Commits
+# ✅ Conventional Commits
 
-This workflow checks that pull request titles follow the [Conventional Commits](https://www.conventionalcommits.org/) specification.
+📝 This workflow checks that pull request titles follow the [Conventional Commits](https://www.conventionalcommits.org/) specification.
 
-## Secrets
+## 🔒 Secrets
 
 ### `GITHUB_TOKEN`
 
 **Required** The GitHub token to use for authentication.
 
-## Example usage
+## 📋 Example Usage
 
 ```yaml
 name: Lint PR Title
@@ -25,4 +25,4 @@ jobs:
     uses: iExecBlockchainComputing/github-actions-workflows/.github/workflows/[email protected]
     secrets:
       GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
+```

conventional-commits/version.txt

@@ -0,0 +1 @@
+1.0.0

docker-build/README.md

@@ -1,6 +1,8 @@
-# Docker build
+# 🐳 Docker Build
 
-## Inputs
+📝 This workflow builds a Docker image from a Dockerfile and pushes it to Docker Hub.
+
+## ⚙️ Inputs
 
 ### `dockerfile`
 
@@ -10,7 +12,7 @@
 
 **Required** The tag to apply to the built image.
 
-## Secrets
+## 🔒 Secrets
 
 ### `dockerhub_username`
 
@@ -20,7 +22,7 @@
 
 **Required** The personal access token to use to log in to Docker Hub.
 
-## Example usage
+## 📋 Example Usage
 
 ```yaml
 uses: iExecBlockchainComputing/github-actions-workflows/[email protected]

rust-build/README.md

@@ -1,15 +1,15 @@
-# Rust Build Workflow
+# 🦀 Rust Build Workflow
 
-A reusable GitHub Actions workflow for building, testing, and publishing Rust packages.
+📝 A reusable GitHub Actions workflow for building, testing, and publishing Rust packages.
 
-## Features
+## ✨ Features
 
 - Build and test Rust packages
 - Cache dependencies for faster builds
 - Publish packages to crates.io
 - Upload build artifacts
 
-## Usage
+## 📋 Usage
 
 ```yaml
 name: Rust CI
@@ -28,7 +28,7 @@ jobs:
       artifact-path: 'target/release/my-app'
 ```
 
-## Inputs
+## ⚙️ Inputs
 
 | Name                | Description                                        | Default   | Required                            |
 |---------------------|----------------------------------------------------|-----------|-------------------------------------|
@@ -40,13 +40,13 @@ jobs:
 | `artifact-name`     | Name of the artifact to upload                     | -         | Only if `upload-artifact` is `true` |
 | `artifact-path`     | Path to the artifact to upload                     | -         | Only if `upload-artifact` is `true` |
 
-## Secrets
+## 🔒 Secrets
 
 | Name              | Description                       | Required                              |
 |-------------------|-----------------------------------|---------------------------------------|
 | `CRATES_IO_TOKEN` | Token for publishing to crates.io | Only if `publish-crates-io` is `true` |
 
-## Examples
+## 📚 Examples
 
 ### Basic Build and Test
 
@@ -78,4 +78,4 @@ jobs:
       publish-crates-io: true
     secrets:
       CRATES_IO_TOKEN: ${{ secrets.CRATES_IO_TOKEN }}
-```
+```

rust-build/version.txt

@@ -0,0 +1 @@
+1.0.0

stale/README.md

@@ -1,7 +1,28 @@
-# Docker build
+# 🧹 Stale
 
-## Example usage
+📝 This workflow marks and closes stale issues and pull requests that have had no activity for a specified period of time.
+
+## 📋 Example Usage
 
 ```yaml
-uses: iExecBlockchainComputing/github-actions-workflows/[email protected]
+name: Mark stale issues and pull requests
+
+on:
+  schedule:
+    - cron: '0 0 * * *'  # Run daily at midnight
+
+jobs:
+  stale:
+    uses: iExecBlockchainComputing/github-actions-workflows/[email protected]
 ```
+
+## ⚙️ Default Configuration
+
+This workflow uses GitHub's built-in stale action with the following default settings:
+
+- Issues and pull requests with no activity for 60 days are marked as stale
+- Stale issues and pull requests are closed after 7 days of inactivity
+- Issues with the "pinned" label are never marked as stale
+- A comment is posted when an issue or pull request is marked as stale
+
+For more information, see the [GitHub documentation on the stale action](https://github.com/actions/stale).