{"id":19522886,"url":"https://github.com/techwatching/hello-github-actions2","last_synced_at":"2026-03-19T10:17:23.800Z","repository":{"id":174881268,"uuid":"624521055","full_name":"TechWatching/hello-github-actions2","owner":"TechWatching","description":null,"archived":false,"fork":false,"pushed_at":"2023-06-13T04:24:52.000Z","size":37,"stargazers_count":0,"open_issues_count":1,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-10-10T20:12:50.723Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/TechWatching.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-04-06T16:49:21.000Z","updated_at":"2023-04-06T16:49:21.000Z","dependencies_parsed_at":"2023-07-06T08:00:35.833Z","dependency_job_id":null,"html_url":"https://github.com/TechWatching/hello-github-actions2","commit_stats":null,"previous_names":["techwatching/hello-github-actions2"],"tags_count":0,"template":false,"template_full_name":"skills/hello-github-actions","purl":"pkg:github/TechWatching/hello-github-actions2","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TechWatching%2Fhello-github-actions2","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TechWatching%2Fhello-github-actions2/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TechWatching%2Fhello-github-actions2/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TechWatching%2Fhello-github-actions2/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/TechWatching","download_url":"https://codeload.github.com/TechWatching/hello-github-actions2/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TechWatching%2Fhello-github-actions2/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29523436,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-16T21:45:09.491Z","status":"ssl_error","status_checked_at":"2026-02-16T21:44:58.452Z","response_time":115,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-11T00:41:26.072Z","updated_at":"2026-02-16T23:01:49.136Z","avatar_url":"https://github.com/TechWatching.png","language":null,"readme":"\u003c!--\n  \u003c\u003c\u003c Author notes: Header of the course \u003e\u003e\u003e\n  Include a 1280x640 image, course title in sentence case, and a concise description in emphasis.\n  In your repository settings: enable template repository, add your 1280x640 social image, auto delete head branches.\n  Add your open source license, GitHub uses Creative Commons Attribution 4.0 International.\n--\u003e\n\n# Hello GitHub Actions 🤣\n\n_Create a GitHub Action and use it in a workflow._\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Start of the course \u003e\u003e\u003e\n  Include start button, a note about Actions minutes,\n  and tell the learner why they should take the course.\n  Each step should be wrapped in \u003cdetails\u003e/\u003csummary\u003e, with an `id` set.\n  The start \u003cdetails\u003e should have `open` as well.\n  Do not use quotes on the \u003cdetails\u003e tag attributes.\n--\u003e\n\n\u003cdetails id=0\u003e\n\u003csummary\u003e\u003ch2\u003eWelcome\u003c/h2\u003e\u003c/summary\u003e\n\nAutomation is key for streamlining your work processes, and [GitHub Actions](https://docs.github.com/actions) is the best way to supercharge your workflow.\n\n- **Who is this for**: Developers, DevOps engineers, students, managers, teams, GitHub users.\n- **What you'll learn**: How to create workflow files, trigger workflows, and find workflow logs.\n- **What you'll build**: An Actions workflow that will check emoji shortcode references in Markdown files.\n- **Prerequisites**: In this course you will work with issues and pull requests, as well as edit files. We recommend you take the [Introduction to GitHub](https://github.com/skills/introduction-to-github) course first.\n- **How long**: This course is five steps long and can be finished in less than two hours.\n\n## How to start this course\n\n1. Right-click **Start course** and open the link in a new tab.\n   \u003cbr /\u003e[![start-course](https://user-images.githubusercontent.com/1221423/218596841-0645fe1a-4aaf-4f51-9ab3-8aa2d3fdd487.svg)](https://github.com/skills/hello-github-actions/generate)\n2. In the new tab, follow the prompts to create a new repository.\n   - For owner, choose your personal account or an organization to host the repository.\n   - We recommend creating a public repository—private repositories will [use Actions minutes](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions).\n   ![Create a new repository](https://user-images.githubusercontent.com/1221423/218594143-e60462b6-9f2a-4fa3-80de-063ac5429aab.png)\n3. 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.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 1 \u003e\u003e\u003e\n  Choose 3-5 steps for your course.\n  The first step is always the hardest, so pick something easy!\n  Link to docs.github.com for further explanations.\n  Encourage users to open new tabs for steps!\n--\u003e\n\n\u003cdetails id=1\u003e\n\u003csummary\u003e\u003ch2\u003eStep 1: Create a workflow file\u003c/h2\u003e\u003c/summary\u003e\n\n_Welcome to \"Hello GitHub Actions\"! :wave:_\n\n**What is _GitHub Actions_?**: GitHub Actions is a flexible way to automate nearly every aspect of your team's software workflow. You can automate testing, continuously deploy, review code, manage issues and pull requests, and much more. The best part, these workflows are stored as code in your repository and easily shared and reused across teams. To learn more, check out these resources:\n\n-  The GitHub Actions feature page, see  [GitHub Actions](https://github.com/features/actions).\n-  The \"GitHub Actions\" user documentation, see [GitHub Actions](https://docs.github.com/actions).\n\n**What is a _workflow_?**: A workflow is a configurable automated process that will run one or more jobs. Workflows are defined in special files in the `.github/workflows` directory and they execute based on your chosen event. For this exercise, we'll use a `pull_request` event. \n\n- To read more about workflows, jobs, and events, see \"[Understanding GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions)\".\n- If you want to learn more about the `pull_request` event before using it, see \"[pull_request](https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#pull_request)\".\n\nTo get you started, we used actions to go ahead and made a branch and pull request for you.\n\n### :keyboard: Activity: Create a workflow file\n\n1. Open a new browser tab, and navigate to this same repository. Then, work on the steps in your second tab while you read the instructions in this tab.\n1. Create a pull request to view all the changes you'll make throughout this course. Click the **Pull Requests** tab, click **New pull request**, set `base: main` and `compare:welcome-workflow`, click **Create pull request**.\n1. Navigate to the **Code** tab.\n1. From the **main** branch dropdown, click on the **welcome-workflow** branch.\n1. Navigate to the `.github/workflows/` folder, then select **Add file** and click on **Create new file**.\n1. In the **Name your file...** field, enter `welcome.yml`.\n1. Add the following content to the `welcome.yml` file:\n   ```yaml\n   name: Post welcome comment\n   on:\n     pull_request:\n       types: [opened]\n   permissions:\n     pull-requests: write\n   ```\n1. To commit your changes, click **Commit new file**.\n1. Wait about 20 seconds for actions to run, then refresh this page (the one you're following instructions from) and an action will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 2 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n  Historic note: The previous course had troubleshooting steps for people not using the GitHub UI.\n--\u003e\n\n\u003cdetails id=2\u003e\n\u003csummary\u003e\u003ch2\u003eStep 2: Add a job to your workflow file\u003c/h2\u003e\u003c/summary\u003e\n\n_Nice work! :tada: You added a workflow file!_\n\nHere's what it means:\n\n- `name: Post welcome comment` gives your workflow a name. This name appears on any pull request or in the Actions tab of your repository.\n- `on: pull_request: types: [opened]` indicates that your workflow will execute anytime a pull request opens in your repository.\n- `permissions` assigns the workflow permissions to operate on the repository\n- `pull-requests: write` gives the workflow permission to write to pull requests. This is needed to create the welcome comment. \n\nNext, we need to specify jobs to run.\n\n**What is a _job_?**: A job is a set of steps in a workflow that execute on the same runner (a runner is a server that runs your workflows when triggered). Workflows have jobs, and jobs have steps. Steps are executed in order and are dependent on each other. We'll add steps in the next step of this exercise. To read more about jobs, see \"[Jobs](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions#jobs)\".\n\nIn this step of our exercise, we will add a \"build\" job. We will specify `ubuntu-latest` as the fastest and cheapest job runner available. If you want to read more about why we'll use that runner, see the code explanation for the line `runs-on: ubuntu-latest` in the \"[Understanding the workflow file](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions#understanding-the-workflow-file)\" article.\n\n### :keyboard: Activity: Add a job to your workflow file\n\n1. Open your `welcome.yml` file. \n2. Update the contents of the file to:\n   ```yaml\n   name: Post welcome comment\n   on:\n     pull_request:\n       types: [opened]\n   permissions:\n     pull-requests: write\n   jobs:\n     build:\n       name: Post welcome comment\n       runs-on: ubuntu-latest\n   ```\n3. Click **Start commit** in the top right of the workflow editor.\n4. Type your commit message and commit your changes directly to your branch.\n5. Wait about 20 seconds for actions to run, then refresh this page (the one you're following instructions from) and an action will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 3 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n--\u003e\n\n\u003cdetails id=3\u003e\n\u003csummary\u003e\u003ch2\u003eStep 3: Add actions to your workflow file\u003c/h2\u003e\u003c/summary\u003e\n\n_Nice work adding a job to your workflow! :dancer:_\n\nWorkflows have jobs, and jobs have steps. So now we'll add steps to your workflow.\n\n**What are _steps_?**: Actions steps will run during our job in order. Each step is either a shell script that will be executed, or an action that will be run. Each step must pass for the next step to run. Actions steps can be used from within the same repository, from any other public repository, or from a published Docker container image.\n\nIn our action, we post a comment on the pull request using a [bash](https://en.wikipedia.org/wiki/Bash_%28Unix_shell%29) script and [GitHub CLI](https://cli.github.com/).\n\n### :keyboard: Activity: Add Actions steps to your workflow file\n\n1. Open your `welcome.yml` file.\n2. Update the contents of the file to:\n   ```yaml\n   name: Post welcome comment\n   on:\n     pull_request:\n       types: [opened]\n   permissions:\n     pull-requests: write\n   jobs:\n     build:\n       name: Post welcome comment\n       runs-on: ubuntu-latest\n       steps:\n         - run: gh pr comment $PR_URL --body \"Welcome to the repository!\"\n           env:\n             GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n             PR_URL: ${{ github.event.pull_request.html_url }}\n   ```\n3. Click **Start commit** in the top right of the workflow editor.\n4. Type your commit message and commit your changes directly to your branch.\n5. Wait about 20 seconds for actions to run, then refresh this page (the one you're following instructions from) and an action will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 4 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n--\u003e\n\n\u003cdetails id=4\u003e\n\u003csummary\u003e\u003ch2\u003eStep 4: Merge your workflow file\u003c/h2\u003e\u003c/summary\u003e\n\n_You're now able to write and run an Actions workflow! :sparkles:_\n\nMerge your changes so the action will be a part of the `main` branch.\n\n### :keyboard: Activity: Merge your workflow file\n\n1. In your repo, click on the **Pull requests** tab.\n1. Click on the pull request you created in step 1.\n1. Click **Merge pull request**, then click **Confirm merge**.\n1. Optionally, click **Delete branch** to delete your `welcome-workflow` branch.\n1. Wait about 20 seconds for actions to run, then refresh this page (the one you're following instructions from) and an action will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 5 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n--\u003e\n\n\u003cdetails id=5\u003e\n\u003csummary\u003e\u003ch2\u003eStep 5: Trigger the workflow\u003c/h2\u003e\u003c/summary\u003e\n\n_You've now got a fully functioning workflow! :smile:_\n\nYour new action will run any time a pull request has been opened.\n\n**Seeing your _action_ in action**: The status of your action is shown in a pull request before you merge, look for **All checks have passed** when you try out the steps below. You can also view them from the **Actions** tab in your repository. From there, you will see all the actions that have run, and you can click on each action to view details and access log files.\n\n![View an action's log](https://user-images.githubusercontent.com/16547949/62388049-4e64e600-b52a-11e9-8bf5-db0c5452360f.png)\n\n### :keyboard: Activity: Trigger the workflow\n\n1. Make a new branch named `test-workflow`.\n1. Commit any change to your branch, such as adding an emoji to your README.md file.\n2. Create the pull request on your branch.\n3. See your action run on your pull request.\n4. Wait about 20 seconds for actions to run, then refresh this page (the one you're following instructions from) and an action will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Finish \u003e\u003e\u003e\n  Review what we learned, ask for feedback, provide next steps.\n--\u003e\n\n\u003cdetails id=X open\u003e\n\u003csummary\u003e\u003ch2\u003eFinish\u003c/h2\u003e\u003c/summary\u003e\n\n_Congratulations friend, you've completed this course!_\n\n\u003cimg src=https://octodex.github.com/images/jetpacktocat.png alt=celebrate width=300 align=right\u003e\n\nHere's a recap of all the tasks you've accomplished in your repository:\n\n- You've created your first GitHub Actions workflow file.\n- You learned where to make your workflow file.\n- You created an event trigger, a job, and steps for your workflow.\n- You're ready to automate anything you can dream of.\n\n### What's next?\n\n- Learn more about GitHub Actions by reading \"[Learn GitHub Actions](https://docs.github.com/actions/learn-github-actions)\".\n- Use actions created by others in [awesome-actions](https://github.com/sdras/awesome-actions).\n- We'd love to hear what you thought of this course [in our discussion board](https://github.com/skills/.github/discussions).\n- [Take another GitHub Skills course](https://github.com/skills).\n- Learn more about GitHub by reading the \"[Get started](https://docs.github.com/get-started)\" docs.\n- To find projects to contribute to, check out [GitHub Explore](https://github.com/explore).\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Footer \u003e\u003e\u003e\n  Add a link to get support, GitHub status page, code of conduct, license link.\n--\u003e\n\n---\n\nGet help: [Post in our discussion board](https://github.com/skills/.github/discussions) \u0026bull; [Review the GitHub status page](https://www.githubstatus.com/)\n\n\u0026copy; 2022 GitHub \u0026bull; [Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) \u0026bull; [MIT License](https://gh.io/mit)\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftechwatching%2Fhello-github-actions2","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftechwatching%2Fhello-github-actions2","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftechwatching%2Fhello-github-actions2/lists"}