Revert "chore: Revert updates to honor maintenance mode"#1150
Revert "chore: Revert updates to honor maintenance mode"#1150FidelusAleksander merged 1 commit intomainfrom
Conversation
This reverts commit cbf6fc5.
There was a problem hiding this comment.
Pull request overview
This PR reverts the previous “revert” and restores the updated GitHub Pages Skills content and automation, converting the repository from an older multi-branch course flow to a streamlined exercise driven directly from main using the skills/exercise-toolkit.
Changes:
- Simplifies
README.mdto describe the exercise model, direct “Copy Exercise” flow, and updated support information. - Replaces the old step-tracking GitHub Actions (using
-step.txtandmy-pagesbranch) with a new chain of step workflows (0-start-exercisethrough4-step) built onskills/exercise-toolkitand operating on themainbranch. - Rewrites the learner-facing step markdown files in
.github/steps/to match the new step sequence and exercise behavior, including a new final review step.
Reviewed changes
Copilot reviewed 26 out of 27 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Updates intro, step overview, and “how to start” instructions to describe the exercise-based flow and new copy badge. |
| .gitignore | Adds a trailing newline; no functional impact. |
| .github/workflows/0-start-exercise.yml | Introduces initial exercise kickoff workflow using skills/exercise-toolkit, creates starter _config.yml and index.md, posts the first step, and enables the Step 1 workflow. |
| .github/workflows/1-step.yml | New workflow that reacts to Pages builds, posts step 1 completion messaging, provides step 2 instructions, and advances to the Step 2 workflow. |
| .github/workflows/2-step.yml | New workflow that reacts to changes in index.md on main, posts step 2 completion messaging and step 3 content, and enables the Step 3 workflow. |
| .github/workflows/3-step.yml | New workflow that validates _config.yml contains theme: minima, reports results back to the exercise issue, posts step 4 content, and enables the Step 4 workflow. |
| .github/workflows/4-step.yml | New workflow that reacts to blog post creation in _posts/ on main, posts the final review content, disables itself, and calls the shared finish-exercise workflow. |
| .github/workflows/0-welcome.yml, 1-enable-github-pages.yml, 2-configure-your-site.yml, 3-customize-your-homepage.yml, 4-create-a-blog-post.yml, 5-merge-your-pull-request.yml | Remove the legacy, branch-based course workflows that relied on -step.txt and the my-pages branch. |
| .github/steps/1-step.md | New step 1 instructions explaining what GitHub Pages is and how to enable it on main. |
| .github/steps/2-step.md | New step 2 instructions guiding learners to customize index.md on main and view the published site; contains updated tip URLs and placeholders for user/repo names. |
| .github/steps/3-step.md | New step 3 instructions describing _config.yml and the minima theme, plus an example config block; includes a minor markdown typo on “main branch`”. |
| .github/steps/4-step.md | New step 4 instructions for creating a Jekyll blog post on main, including proper _posts/YYYY-MM-DD-title.md naming and front matter guidance. |
| .github/steps/x-review.md | New final review content summarizing what the learner accomplished and linking to further resources. |
| .github/steps/0-welcome.md, 1-enable-github-pages.md, 2-configure-your-site.md, 3-customize-your-homepage.md, 4-create-a-blog-post.md, 5-merge-your-pull-request.md, X-finish.md, -step.txt | Remove legacy course-style step markdown and the numeric step state file in favor of exercise-toolkit–driven flow. |
| .github/dependabot.yml | Removes Dependabot configuration for GitHub Actions updates. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 1. Enable GitHub Pages | ||
| 2. Configure your site | ||
| 3. Customize your home page | ||
| 4. Create a blog post | ||
| 5. Merge your pull request | ||
|
|
||
| ### How to start this course | ||
|
|
||
| <!-- For start course, run in JavaScript: | ||
| 'https://github.com/new?' + new URLSearchParams({ | ||
| template_owner: 'skills', | ||
| template_name: 'github-pages', | ||
| owner: '@me', | ||
| name: 'skills-github-pages', | ||
| description: 'My clone repository', | ||
| visibility: 'public', | ||
| }).toString() | ||
| --> | ||
|
|
||
| [](https://github.com/new?template_owner=skills&template_name=github-pages&owner=%40me&name=skills-github-pages&description=My+clone+repository&visibility=public) | ||
|
|
||
| 1. Right-click **Start course** and open the link in a new tab. | ||
| 2. In the new tab, most of the prompts will automatically fill in for you. | ||
| - For owner, choose your personal account or an organization to host the repository. | ||
| - We recommend creating a public repository, as private repositories will [use Actions minutes](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions). | ||
| - Scroll down and click the **Create repository** button at the bottom of the form. | ||
| 3. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. | ||
|
|
||
| <footer> | ||
|
|
||
| <!-- | ||
| <<< Author notes: Footer >>> | ||
| Add a link to get support, GitHub status page, code of conduct, license link. | ||
| --> | ||
| 1. Configure your site | ||
| 1. Customize your home page | ||
| 1. Create a blog post | ||
| 1. Merge your pull request |
There was a problem hiding this comment.
The high-level step list here no longer matches the actual exercise flow: steps 2 and 3 are listed as "Configure your site" and "Customize your home page", but the step markdown files define Step 2 as customizing the homepage and Step 3 as configuring the site, and there is no longer a dedicated "Merge your pull request" step since learners work directly on the main branch. Please update this list so the step order and descriptions align with the current Step 1–4 content and remove or reword the pull-request step to avoid confusing learners.
| <details> | ||
| <summary>Having trouble? 🤷</summary><br/> | ||
|
|
||
| - Make sure you are editing the `_config.yml` file in the `main` branch`. |
There was a problem hiding this comment.
There is an extra trailing backtick after the word branch which produces unbalanced code formatting in the rendered markdown; please remove the backtick so the sentence reads "in the main branch."
| - Make sure you are editing the `_config.yml` file in the `main` branch`. | |
| - Make sure you are editing the `_config.yml` file in the `main` branch. |
Reverts #1113