fix: update pkg trigger, update docs, rm release

Author: hnrobert

.github/workflows/package.yml

@@ -1,9 +1,10 @@
 name: Simple Package — Sequential macOS arm64 & Windows x64
 
 on:
-  workflow_dispatch: # manual trigger
+  workflow_dispatch: # you can also manually trigger this workflow
   push:
-    tags: ["v*"]
+    branches:
+      - main
 
 jobs:
   build-macos-arm64:

.github/workflows/release.yml

@@ -14,8 +14,7 @@ requirements.txt
  └─ workflows/
     ├─ test.yml
     ├─ package.yml
-    ├─ package-matrix.yml
-    └─ release.yml
+    └─ package-matrix.yml
 ```
 
 This example includes a package workflow; you'll implement it as a hands-on exercise.
@@ -65,7 +64,7 @@ YAML is a human-friendly data serialization standard for all programming languag
     - develop
   ```
 
-  **Or**
+  **Or the following expression, they are equivalent**
 
   ```yaml
   branches: [main, develop]
@@ -99,7 +98,7 @@ YAML is a human-friendly data serialization standard for all programming languag
 - Comments: Lines starting with `#` are comments and are ignored by parsers.
 
   ```yaml
-  # This is a comment
+  # This is a comment. It looks awesome.
   ```
 
 **Congrats!** You now have a basic understanding of YAML syntax, which is enough for you to read and understand GitHub Actions workflow files.
@@ -151,8 +150,9 @@ To define a job in GitHub Actions, you use the `jobs` keyword followed by a uniq
   - GitHub Actions provides a variety of hosted runners with different operating systems and configurations. The three most common options are:
     - `ubuntu-latest`: The latest stable version of Ubuntu Linux.
     - `windows-latest`: The latest stable version of Windows Server.
-    - `macos-latest`: The latest stable version of macOS.  
-  You can choose a appropriate runner according to [the docs provided by GitHub](https://docs.github.com/en/actions/how-tos/write-workflows/choose-where-workflows-run/choose-the-runner-for-a-job#choosing-github-hosted-runners) based on your project's requirements and the environment you need for your workflows.
+    - `macos-latest`: The latest stable version of macOS.
+    - You can choose a appropriate runner according to [the docs provided by GitHub](https://docs.github.com/en/actions/how-tos/write-workflows/choose-where-workflows-run/choose-the-runner-for-a-job#choosing-github-hosted-runners) based on your project's requirements and the environment you need for your workflows.
+  - You can also set up self-hosted runners if you need specific hardware or software configurations not available in GitHub's hosted runners.
 - `steps`: A list of steps that make up the job. Each step can either run a script or use an action.
 
 #### Steps
@@ -167,14 +167,14 @@ steps:
   # This is a common first step in most workflows that need to work with the repository's code.
   - name: Checkout Repo
     uses: actions/checkout@v4
-  
+
   # Set up Python environment - Automatically install Python for the job efficiently
   # In this way, you don't need to manually install Python using shell commands
   # This action step handles it for you.
   - name: Set up Python
     uses: actions/setup-python@v4
     with:
-      python-version: "3.11"
+      python-version: '3.11'
 
   # Install dependencies
   # This step ensures that all necessary Python packages listed in requirements.txt are installed
@@ -231,20 +231,34 @@ You can try implement a simple sequential workflow that first builds macOS arm64
 
 If you have finished composing or encountered some troubles, you may see `solutions/package.yml` — this builds the two packages in sequence and uploads two artifacts (`hello-macos-arm64` and `hello-windows-x64`).
 
-## Release flow (automatic packaging and release assets)
+## Release flow (automatic packaging and upload assets to release)
 
-The repository includes a pair of workflows to create a tag, publish a release, and attach build artifacts to the release:
+The repository includes a workflow that automatically builds packages for multiple OS/Python combinations and attaches the build artifacts to a GitHub Release.
 
-- `release.yml` — creates a `vX.Y.Z` tag from the workflow_dispatch input and publishes a GitHub Release.
 - `package-matrix.yml` — runs packaging on `ubuntu`, `macos`, and `windows` using a matrix and attaches the build artifacts to the release when the workflow is triggered by the `release` event.
 
-How it works:
+### Wait, your workflow need some permissions to upload assets to release
+
+To allow the workflow to upload assets to a release, you need to grant it the necessary permissions. By default, GitHub Actions workflows have read-only access to the repository contents. To upload assets to a release, you need to ensure that the workflow has write permissions.
+
+#### How to do that
+
+1. Go to your repository on GitHub.
+2. Click on the "Settings" tab.
+3. In the left sidebar, click on "Actions" under the "Security" section.
+4. Scroll down to the "Workflow permissions" section.
+5. Select the option "Read and write permissions".
+6. Click the "Save" button to apply the changes.
+
+### Now try to create a release
+
+1. Go to the Releases section of the repository.
+2. Click on "Draft a new release".
+3. Enter a tag version (e.g., `v1.0.0`) and fill in the release title and description you like.
+4. Click on "Publish release".
 
-1. Use the **Create Release** workflow in the Actions tab.
-2. The workflow will create the tag base on your input and publish the release; this publishes a `release` event.
-3. `package-matrix.yml` is configured to run when a release is published; it will build packages for each OS/Python combination in the matrix and attach each artifact to the release.
+Once the release is published, the `package-matrix.yml` workflow will automatically run (so do the workflow defined by `package.yml` that you have just implemented, but now let's focus on `package-matrix.yml`), building the packages for each OS/Python combination defined in the matrix and attaching the resulting artifacts to the release.
 
-Notes:
+## The end
 
-- The build artifacts are attached to the Release created by `release.yml`.
-- Packaging is also possible manually by running the `Package — Build & Upload using Matrix` workflow.
+Now you may return to our [Weekly Sharing Session Repo](https://github.com/CompPsyUnion/2526-weekly-session/tree/main/Contents/GitHubAction) and continue to the end of our today's session.