Update workflow triggers

Author: lilblueyes

.github/steps/1-step.md

@@ -13,11 +13,12 @@ A branch is a movable pointer to a sequence of commits. You can experiment freel
 3. (Optional CLI)
    ```bash
    git checkout -b my-first-branch
-   <details> <summary>Having trouble? 🤷</summary><br/>
    ```
 
-Make sure you’re on the repository page (not your fork list).
+<details>
+<summary>Having trouble? 🤷</summary><br/>
 
-If using CLI, verify you have Git installed: git --version.
+Make sure you’re on the repository page, not your fork list.  
+If using CLI, verify you have Git installed, `git --version`.
 
 </details>

.github/steps/2-step.md

@@ -14,16 +14,18 @@ A commit records a snapshot of your changes with a message explaining **why** yo
 
 (Optional CLI)
 
-````bash
+```bash
 mkdir -p playground
 printf "Hello, I'm learning GitHub Basics!\n" >> playground/README.md
 git add playground/README.md
 git commit -m "docs: add a short introduction in playground"
 git push origin my-first-branch
-<details> <summary>Having trouble? 🤷</summary><br/>
+```
 
-Ensure you’re on my-first-branch when editing.
+<details>
+<summary>Having trouble? 🤷</summary><br/>
 
-If committing via the web editor, use a clear message (e.g., “docs: add intro”).
+Ensure you’re on `my-first-branch` when editing.  
+If committing via the web editor, use a clear message, for example “docs: add intro”.
 
-</details> ```
+</details>

.github/workflows/0-start-exercise.yml

@@ -1,10 +1,13 @@
 name: Step 0 # Start Exercise
 
 on:
+  # Auto-start lorsque l'élève crée un dépôt depuis la template
+  push:
+    branches: [ main ]
+  # En complément, si la branche par défaut est créée sans commit
+  create:
+  # Garde le déclencheur manuel en secours
   workflow_dispatch:
-  # NOTE: Enable this if your repo is a template and you want auto-start on first push to main
-  # push:
-  #   branches: [ main ]
 
 permissions:
   contents: write

.github/workflows/1-step.yml

@@ -1,10 +1,12 @@
 name: Step 1
 
 on:
+  # Se déclenche quand l'élève crée la branche de l’exercice
+  create:
+  # Optionnel, si la branche est créée par un premier push
+  push:
+    branches: [ my-first-branch ]
   workflow_dispatch:
-  # You can also trigger on branch create/push if desired:
-  # create:
-  # push:
 
 permissions:
   contents: read
@@ -18,11 +20,13 @@ env:
 jobs:
   find_exercise:
     name: Find Exercise Issue
+    if: github.event_name == 'create' && github.event.ref_type == 'branch' && github.event.ref == 'my-first-branch'
     uses: skills/exercise-toolkit/.github/workflows/find-exercise-issue.yml@v0.7.1
 
   post_next_step_content:
     name: Post next step content
     needs: [find_exercise]
+    if: github.event_name == 'create' && github.event.ref_type == 'branch' && github.event.ref == 'my-first-branch'
     runs-on: ubuntu-latest
     env:
       ISSUE_REPOSITORY: ${{ github.repository }}

.github/workflows/2-step.yml

@@ -1,9 +1,12 @@
 name: Step 2
 
 on:
+  # Valide automatiquement les commits sur la branche d’exercice
+  push:
+    branches: [ my-first-branch ]
+    paths:
+      - "playground/**"
   workflow_dispatch:
-  # You can also trigger on push to validate right after commits:
-  # push:
 
 permissions:
   contents: write
@@ -97,7 +100,8 @@ jobs:
 
   post_next_step_content:
     name: Post next step content
-    needs: [find_exercise] # or [find_exercise, check_step_work] if you want to gate progression
+    # Gating, on ne passe à l'étape 3 que si les checks sont OK
+    needs: [find_exercise, check_step_work]
     runs-on: ubuntu-latest
     env:
       ISSUE_REPOSITORY: ${{ github.repository }}

.github/workflows/3-last-step.yml

@@ -1,10 +1,9 @@
 name: Step 3 # Last step of the exercise
 
 on:
+  pull_request:
+    types: [opened, reopened, closed]
   workflow_dispatch:
-  # You can also trigger on PR events:
-  # pull_request:
-  #   types: [opened, reopened, closed]
 
 permissions:
   contents: write
@@ -74,7 +73,9 @@ jobs:
   finish_exercise:
     name: Finish Exercise
     needs: [find_exercise, post_review_content]
+    if: github.event_name == 'pull_request' && github.event.action == 'closed' && github.event.pull_request.merged == true
     uses: skills/exercise-toolkit/.github/workflows/finish-exercise.yml@v0.7.1
     with:
       issue-url: ${{ needs.find_exercise.outputs.issue-url }}
       exercise-title: "GitHub Basics"
+      completion-message: "Congratulations on completing the GitHub Basics exercise! 🎉"

README.md

@@ -1,50 +1,44 @@
-# GitHub Basics
+<header>
 
-Learn the essential GitHub flow:
+# Introduction à GitHub
 
-1. Create a branch
-2. Commit a file
-3. Open a pull request
-4. Merge your pull request
+_Démarre sur GitHub en moins d’une heure._
 
-## Who is this for
+</header>
 
-New contributors who want a hands-on, guided introduction to GitHub collaboration.
+## Bienvenue
 
-## What you'll learn
+Des jeux vidéo aux expériences data, GitHub propulse certains des projets les plus avancés. Que tu débutes ou que tu aies juste besoin d’un rappel, ce mini cours “Introduction à GitHub” te guide pas à pas pour contribuer rapidement.
 
-- Repositories, branches, commits, and pull requests
-- Writing meaningful commit messages
-- Reviewing and merging a pull request
+- **Pour qui**: nouveaux développeurs, nouveaux utilisateurs GitHub, étudiants.
+- **Ce que tu vas apprendre**: dépôts, branches, commits, pull requests.
+- **Ce que tu vas construire**: une petite modification de documentation proposée via une pull request.
+- **Prérequis**: aucun, un compte GitHub suffit.
+- **Durée**: moins d’une heure.
 
-## What you'll build
+Dans ce cours, tu vas:
 
-A small documentation change in this repository, proposed through a pull request.
+1. Créer une branche
+2. Commiter un fichier
+3. Ouvrir une pull request
+4. Merger ta pull request
 
-## Prerequisites
+### Comment démarrer le cours
 
-- A GitHub account
-- No command line or coding experience required (CLI tips are included, but optional)
+> Important, **clique sur le bouton ci-dessous** pour créer un **nouveau dépôt depuis la template**. N’utilise pas “Fork”, sinon les Actions risquent de ne pas se lancer automatiquement. Les dépôts privés consomment des minutes GitHub Actions.
 
-## How long
+[![Commencer le cours](https://img.shields.io/badge/Commencer%20le%20cours-%E2%86%92-1f883d?style=for-the-badge&logo=github&labelColor=197935)](https://github.com/new?template_owner=clubrobenstabrest&template_name=github-basics&owner=%40me&name=github-basics&description=Exercice%3A%20GitHub%20Basics&visibility=public)
 
-This exercise typically takes **15–30 minutes**.
+1. Clic droit sur **Commencer le cours** puis “Ouvrir le lien dans un nouvel onglet”.
+2. Dans le nouvel onglet, la plupart des champs sont préremplis, choisis le propriétaire du dépôt.
+3. Clique sur **Create repository** en bas du formulaire.
+4. Attends environ **20 secondes**, puis **rafraîchis** la page, les instructions étape par étape apparaîtront dans les Issues.
 
-## How to start this exercise
-
-Copy this exercise to your account, wait about **20 seconds**, then refresh the page:
-[![](https://img.shields.io/badge/Copy%20Exercise-%E2%86%92-1f883d?style=for-the-badge&logo=github&labelColor=197935)](https://github.com/new?template_owner=clubrobenstabrest&template_name=github-basics&owner=%40me&name=github-basics&description=Exercise%3A%20GitHub%20Basics&visibility=public)
-
-<details>
-<summary>Having trouble? 🤷</summary><br/>
-
-- Choose your personal account (or an organization) as the owner.
-- Public repositories are recommended (private repos consume Actions minutes).
-- If it isn’t ready in 20s, open the <a href="../../actions">Actions</a> tab to check the run.
-- If a job failed, please open an issue — you found a bug! 🐛
+---
 
-</details>
+## Support
 
----
+Besoin d’aide, ouvre une issue dans ce dépôt.  
+Statut de GitHub, [status.github.com](https://www.githubstatus.com/)
 
 &copy; 2025 GitHub • [Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) • [MIT License](https://gh.io/mit)