Learn GITHUB-ACTIONS with Real Code Examples

No installation required for GitHub-hosted runners

Optional: set up self-hosted runners for custom environments

Configure repository access and permissions

Create `.github/workflows/` directory

Add YAML workflow files defining jobs and steps

GitHub repository with Actions enabled

Optional self-hosted runner setup

Configure secrets and environment variables

Create workflow YAML files in `.github/workflows/`

Test workflows using manual or event triggers

.github/workflows/*.yml - workflow files

Optional scripts/ folder for reusable shell scripts

Secrets configured in repository settings

Artifact directories defined in workflow

README.md referencing workflow usage

gh workflow list - list workflows

gh workflow run - manually trigger workflow

gh run view - view workflow run logs

gh run watch - watch workflow progress

gh run rerun - rerun workflow

Workflow YAML UTF-8 compatible

Secrets and environment variables support multiple languages

Logs can contain multi-language output

Marketplace actions support global users

GitHub interface available in multiple languages

Web-based interface in GitHub repository

CLI access via GitHub CLI

Integration with VS Code extensions

Workflow visualization accessible to contributors

Actions can be triggered programmatically via API

GitHub Actions tab provides graphical visualization

Logs display step-by-step execution

No additional UI styling required

Marketplace provides workflow and action previews

Third-party dashboards available via integrations

Artifacts and caches preserve workflow state

Secrets securely manage sensitive info

Job statuses indicate success/failure

Workflow logs provide historical state

Matrix builds track per-environment execution

Artifacts store build outputs

Caches store dependencies for faster runs

Logs track step outputs for debugging

Secrets manage secure credentials

Workflow outputs can be shared between jobs