Nice work!

You've created your first GitHub Action and this course is now complete! I'll stop responding but the fun doesn't have to stop here.

Want to keep learning?

In this repository:

• Your merge should trigger your action again, check it out in the Actions tab.
• The Dockerfile contains metadata for your action. Try changing some of that. You could, for example, change the icon that displays when the action is running.
• Change the MY_NAME environment variable to use your name instead of Mona's in .github/workflows/main.yml.
• Change the contents of entrypoint.sh to output a different message.

Outside of this repository:

• Review the GitHub Actions documentation on the GitHub Developer site.
• Use existing actions from the GitHub Marketplace.
• Use existing actions from GitHub's official actions community.
• Use actions created by others in awesome-actions.

Now...what will you learn next?

Welcome

This course helps you create a simple GitHub Action and use that action in a workflow.

What are GitHub Actions?

GitHub Actions are a flexible way to automate nearly every aspect of your team's software workflow. Here are just a few of the ways teams are using GitHub Actions:

• Automated testing (CI)
• Continuous delivery and deployment
• Responding to workflow triggers using issues, @ mentions, labels, and more
• Triggering code reviews
• Managing branches
• Triaging issues and pull requests

The sky is truly the limit with GitHub Actions.

The best part, these workflows are stored as code in your repository and easily shared and reused across teams.

To learn even more, check out the GitHub Actions feature page, or the GitHub Actions documentation.

Before you begin

In this course you will work with issues and pull requests, as well as edit files. If these things are not familiar to you, we recommend you take the Introduction to GitHub course, first!